Jira ticket not showing in the backlog? 7 causes

The short answer

The backlog is not a list of everything in the space. It is a view of one board, and it only shows a work item when the item matches the board's filter, its status is mapped to a column, that column is not the last (Done) column, and the item is not a subtask. Atlassian adds a board-wide condition: at least one status must be mapped to the right-most column. If any one of those fails, the item exists but stays off the backlog. Filters you turned on yourself can hide it too.

So when a ticket is missing, first search for its key to prove it exists. Then work through the causes below in order. Causes 1 and 2 you can fix yourself. From cause 4 on, you may need a board admin or space admin.

If the whole Backlog tab is missing on a kanban board, skip to No Backlog tab at all.

How the backlog decides what to show

Atlassian's help for the scrum backlog lists the conditions a work item has to meet to appear there. Put side by side with a board, it looks like this:

Keep this table in mind and most "missing" tickets explain themselves. The backlog was built to show work that still needs planning, so finished work and pieces of other work are left out on purpose.

Cause 1: It is in a sprint, not the Backlog section

On a scrum board, the Backlog page shows the space's work items grouped into a backlog and sprints. The section labelled Backlog sits at the bottom, below the active sprint and any future sprints. A ticket that someone already dragged into a sprint is on the same page, just higher up.

Example: Jonas creates PAY-142, "Show refund date on receipts", and cannot find it under Backlog. Ana planned it into Sprint 15 yesterday, so it is in the Sprint 15 section near the top.

Fix: scroll up through every sprint section on the Backlog page. If the ticket is in the active sprint, you will also find it on the board. The difference between the two lists is in backlog vs sprint.

Cause 2: A filter on the backlog is hiding it

The backlog has its own filters, and they stay on until you clear them. Quick filters show as buttons above the backlog. The backlog also has an epic filter and a version filter, each with a dropdown, and you can open an epic panel and a version panel beside the list. A selected epic, version or quick filter narrows the list to matching work items, and a ticket outside it disappears.

Atlassian also notes that view settings are applied per user. Your view can hide things your colleague's view shows, which explains "I can see it, why can't you?"

Fix:

1. Turn off every quick filter button above the backlog.
2. Open the epic filter and version filter dropdowns and clear any selection.
3. Clear the search box if your backlog has one.
4. Look again before you ask an admin anything.

Cause 3: Its status is in the Done column

Atlassian's scrum backlog help says a work item's status must map to a column, "but not the Done column", to appear. A ticket in Done, or in any status mapped to the last column, never appears in the Backlog section or in a future sprint. Atlassian's Data Center troubleshooting article calls this expected behaviour: moving the item to a status outside the Done column, or starting the sprint, makes it visible, because an active sprint does show its Done work items. So a finished ticket in the active sprint stays listed in that sprint's section; only finished tickets outside it drop out.

This catches teams who map extra statuses to the last column. Atlassian's column help says Jira only treats work in the right-most column as complete, and suggests mapping statuses such as Canceled there. That is right for the board, but those tickets also vanish from the backlog.

Example: Tom closed PAY-118 as Won't Do last month. Now Ana wants it back for next quarter and cannot find it in the backlog, because Won't Do sits in the Done column.

Fix: search for the key, open the ticket, and move it back to a To Do status. The change status guide shows how, and Done vs Closed vs Resolved explains why one board can have several finished statuses.

Cause 4: Its status is not mapped to any column

This is the answer to "Jira status not showing in backlog". Every status in the workflow has to be placed in a board column. Atlassian's column help is direct: "Unmapped statuses will hide work items both in your board view and backlog view." It happens when someone adds a status to the workflow, such as Waiting for Vendor, and nobody adds it to the board.

How to spot it: open the ticket and read its status. If no column on the board holds that status, it is unmapped.

Fix (board admin):

1. Select More actions (•••) next to the board name, then Board settings.
2. Open Layout, then Columns.
3. Drag the status from the Unmapped statuses panel into the right column.

Atlassian is rolling out a new board view to company-managed spaces, so the menu labels on your board may differ slightly. How statuses and columns relate is covered in Jira workflow explained.

Cause 5: Every status sits in the first column

A less obvious one. Atlassian's scrum backlog help says that if every status maps to the first column, you will not see any work items in the scrum backlog. The same help also requires at least one status mapped to the right-most column, so the last column cannot be left empty either. The kanban backlog help gives the same first-column warning, and adds that a status also has to map to the next column on the board for items to appear in the Backlog section.

This shows up when a board was set up quickly with one column holding everything. The symptom is a backlog that is empty for everyone, not one missing ticket.

Fix (board admin): in Columns (see Cause 4 for the path), spread the statuses across at least two columns, for example To Do in the first and In Progress in the second, and make sure the right-most column holds at least one status, such as Done.

Cause 6: It is a subtask

Searches like "Jira backlog not showing subtasks" have a simple answer. The scrum backlog help lists "the work item isn't a subtask" as a condition, so subtasks do not appear as their own rows. They belong to a parent story or task. In some backlog views you can expand a parent to see its subtasks: the kanban backlog help says subtasks appear when you expand their parent, and the view settings include Expand all to show all subtasks in the backlog.

Fix: find the parent ticket and expand it or open it. If the work really is its own piece of work, it may be better as a task than a subtask; Jira subtasks explained helps you decide.

Cause 7: The board's filter leaves it out

Every company-managed board runs on a saved filter, and Atlassian's help says a work item must match it to appear in the backlog. Atlassian's Data Center article puts it plainly: the board's filter controls the visibility of work everywhere on the board. A board for the receipts team might only include tickets with the Receipts component. Jonas's PAY-142 has no component, so it never appears, on the board or in the backlog.

The same applies to stories in another space: if a ticket's key starts with different letters, it may simply belong to a different board. The board vs project guide explains how boards pull work from spaces.

Fix: compare the missing ticket with one that does show. If they differ in component, label, work type or space, adjust the ticket. If you cannot see a pattern, ask the board admin to check the board's filter. For the related problem on the board itself, see ticket not showing on the board.

No Backlog tab at all (kanban)

If you search "Jira kanban backlog not showing", one reason is that the kanban board has no backlog switched on. Atlassian notes that the kanban backlog must be enabled for a particular board before its users can use it. How you turn it on depends on the space type. To check yours, select More actions (•••) next to the space name; the space details are at the bottom of that menu.

Team-managed space

1. In the space navigation, select the add-to-navigation icon, then Backlog.
2. Select Add to navigation.

A Backlog tab appears in the space navigation, and work items created with + Create in the top bar land in the backlog. If you later remove it, Atlassian says all work items move to the board, into the column that matches their status.

Company-managed space

A Jira admin or board admin opens Board settings > Layout > Columns and drags an existing status onto the Kanban backlog panel, or creates a new status and drops it there. Work items in that status then show in the backlog instead of on the board.

Once the backlog exists, Cause 5 applies to kanban too: an item shows in the Backlog section only if its status maps to the kanban backlog column and the next column on the board is mapped as well.

Who can fix what

When you ask an admin, send the ticket key, its status, and which board you expected it on. With those three facts, they can check the causes above without asking you again.

Practise finding work fast

Every check above starts the same way: search for the key and read the ticket's status before you ask anyone. Agile Board Practice has a short lesson on exactly that, where a colleague mentions PAY-131, you search for it by key, read its status and epic, then search by words and clear the search again. Another lesson has you filter a board to one person and clear the filter, so a hidden filter never fools you twice.