Jira Backlog: Why Work Items Go Missing and How to Fix It

Here's the catch. A work item only shows in the scrum backlog if four things are all true, and getting one wrong can make the whole list look empty. Map every status to the first column, for example, and the backlog looks blank even though nothing's been deleted.

Four reasons a work item won't show in the backlog

Atlassian's rule is that a work item appears only if it isn't a subtask, it matches the board's saved filter, its status is mapped to a board column other than Done, and at least one status is mapped to the right-most column.

Reason a work item is missing	Fix
It's a subtask	Subtasks never show in the backlog; open the parent instead
It doesn't match the board's filter	Edit the board's saved filter
Its status is mapped to the Done column	Move that status to an earlier column
Nothing is mapped to the right-most column	Map at least one status there

Work through the table in that order. The subtask check takes seconds. The filter is the next most likely culprit, especially if someone has changed which spaces or labels the board pulls in. Column mapping comes last because it's the one that hides everything at once, and it's easy to break while tidying up a board's columns.

Who's allowed to start a sprint

To start a sprint you have to be a space administrator for every space that matches the board's filter. That trips up teams whose board pulls work from more than one space: being admin on your own space isn't enough if the filter reaches into a second one. Different backlog actions need different permissions, so someone who can rank and edit items may still be blocked at the Start sprint button.

Ranking and creating work items

You rank the backlog by dragging work items up or down. For long lists there's a quicker route: right-click a work item and send it to the top or the bottom of the backlog. New items come from + Create work item at the bottom of the backlog or at the bottom of a sprint, so you can add work straight into the sprint you're planning.

Editing straight from the backlog

You don't have to open each work item to change it. Summary, Assignee, Estimate, Parent and Priority can all be edited directly on the backlog. Two keyboard shortcuts make this quicker: J and K move you through the list, and E opens the selected work item for editing.

One thing to know before you plan with estimates: the Story Points field is only available by default on the story and epic work types. If your team logs tasks and bugs and wonders why there's nowhere to put points, that's why.

Bulk editing several work items at once

Select the work items you want with the checkboxes, Ctrl or Command click, or Shift to pick a range. Then choose Edit, then Fields, and Jira opens bulk edit. Each field gives you five options:

• Keep as is
• Add new
• Find and remove
• Replace all
• Remove all

After that you get a confirmation screen before anything changes, which is your chance to catch a mistake across dozens of items. For status changes there's a separate route: select the items and use Edit, then Status to transition them together.

Splitting a work item that's grown too big

Right-click a work item and choose Split work item. The new item keeps the same work type and most of the details, including priority, component and label, so you're not re-entering everything. Where it lands depends on where you split it. Split it in the backlog and the new item stays in the backlog. Split it in a sprint and you choose whether it goes to the backlog or into a sprint.

For a closer look at the related setup, see the best Jira apps.

How to move work from the backlog into a sprint

1. Open the Backlog tab in your scrum space.
2. Create anything missing with Create or + Create work item.
3. Drag to rank, or right-click to send items to the top or bottom.
4. Multi-select and use Edit, then Fields for any bulk changes.
5. Drag work items from the Backlog section into the sprint section, then start the sprint.

Before you start, check the sprint avatars. They show who has work assigned, and More actions shows the sprint workload for each assignee, so you can see one person carrying far more than anyone else before the sprint begins rather than halfway through it.

When you're ready for more, Jira Issue Types is a sensible follow-up.

My verdict on the Jira backlog

I'd spend five minutes on the board filter and column mapping before blaming Jira for a missing work item, because that's where the problem nearly always sits. I'd also get the person running sprints made admin on every space the board pulls from, before planning day. If your team is weighing up whether Jira is the right fit at all, my comparison of Jira and Trello for planning work is the place to start, and here's what Jira's free plan includes.

A tidy backlog makes a team quicker. Getting that team working well with AI is where I come in. I run AI training and workshops for teams, and help businesses with AI enablement, AI automation and GEO, which is about getting your business seen and cited in AI answers. Most of that work is with SaaS marketing teams, telecom companies and small businesses. Here's how we can work together.

Frequently asked questions

Why is my Jira backlog empty?

Usually the board's saved filter or column mapping. A work item only shows if it isn't a subtask, matches the filter, has a status mapped to a column other than Done, and at least one status is mapped to the right-most column.

Why don't subtasks show in the Jira backlog?

Subtasks never appear in the scrum backlog. Open the parent work item to see them.

Who can start a sprint in Jira?

You have to be a space administrator for every space that matches the board's filter.

Can I bulk edit work items in the Jira backlog?

Yes. Multi-select, then choose Edit, then Fields. You can Keep as is, Add new, Find and remove, Replace all or Remove all, with a confirmation screen before anything changes.

What happens when I split a work item?

The new item keeps the same work type and most details, including priority, component and label.