Fix work items missing from a Jira board
Check one missing work item by its key before changing the board. If you can open it but cannot see it on the board, investigate the view’s scope. If you cannot open it at all, first establish whether the key is correct and whether you have access.
Missing work items
Use a known example, such as APP-123, and change one setting at a time.
-
Open the work item directly
Search for its key. If it cannot be opened, ask an administrator or someone who can access it to check permissions, security, and whether it still exists. Do not broaden a board filter to solve an access problem. -
Clear temporary filters
Clear the board search and active quick filters. Expand collapsed lanes or columns. If the card returns, reapply filters individually to find which one excludes it. -
Check the saved filter
Run the board’s saved query in search withAND key = APP-123added before any ordering clause. Preserve parentheses around existing OR conditions. No result means the base selection needs investigation. -
Check placement
Inspect status-to-column mapping, sprint membership, and backlog placement. On Kanban boards, inspect the sub-filter too. A ticket can match the base query yet be outside the active board view.
First separate a hidden card from a work item outside this board’s current scope.
-
Check the key and space
Open the work item from search. Confirm it belongs to the expected space and that you have access. A similar summary is not proof that it is the same ticket. -
Clear view filters
Clear search text and custom filters, then expand collapsed sections. Compare the board with its backlog or List view. -
Check the sprint or backlog
If sprints are enabled, inspect the parent work item’s sprint and whether that sprint is active. For Kanban, check whether the item is still waiting in the backlog. -
Inspect status mapping
Ask the space admin to check Space settings → Board → Columns and statuses. A status with no column mapping can make its work disappear from the board.
Good to know
Keep a short record of the key, expected column, and the check that failed.
- If all users are missing the same status, inspect shared configuration. If only one person is affected, begin with their filters and access.
- Never remove issue security or grant broad access solely to make a card appear. Establish the intended audience first.
- A subtasks-only problem needs a hierarchy check; use the dedicated subtask guide before editing the whole board filter.
FAQ
Why does search find a ticket that the board does not?
Search and board views can have different scope. Check the saved filter, additional filters, mapping, and sprint or backlog placement.
Should I recreate a missing ticket?
First locate the original by key and establish what happened. Recreating it can introduce duplicate work and lose the original history.