How can you see if an issue from a next-gen project is part of the backlog or not in the issues list

[Jon Poploskie]

If I search issues and search for all issues, how can I tell if a particular issue (from a next gen project) is in the backlog or not? Or put another way, how can I search for only backlog items, or only non-backlog items? I cannot see any identifying fields (including in a CSV export of all fields) that identifies if it's backlog or not; the status field shows the same status as the first status of my kanban board.

Thank you!

Jon

[Petter Gonçalves · Accepted solution]

Hello Jon,

The filter for Next-gen boards cannot be changed to display specific issues, so every single issue of the project will be always displayed on the board.

That been said, to identify your issues at the backlog of Scrum next-projects (Both for Scrum and Kanban) you just need to check the Sprint field. All issues that are not added to a Sprint, are automatically in the backlog of your project. JQL function:

Sprint is empty

P.S: You must turn on the Sprint feature to be able to filter.

Let me know if this information helps.

[Jon Poploskie]

Thank you Petterson, I appreciate the help.

Jon

[Petter Gonçalves]

You are welcome, Jon!

[Mark_Price]

How do I solve this if I don;t want to use sprints?  We are a kanban shop, not a scrum shop.  So I don't want sprints, but I DO want to be able to see a status that indicates an issue is in the backlog and not on the board.

[Amir Barkal]

Joining the question and adding:

we would like to see an indicator from within an issue that states that this issue is in the backlog.

currently it’s a weird thing to have an issue with status “TO-DO” while the issue is actually in the backlog...

using a next-gen kanban project.

[Chris Samios]

Unfortunately we're hitting this issue too, on a next-gen project that is not using sprints.

The most frustrating thing is that in adding a task to the backlog, it's still technically in the "Selected" status (our first column). So using "Status" or "Status Category" is out.

I also tried pulling the raw data from the API for a test issue, but the only field that visibly changed between something being in the backlog versus moved to the board was the 'last updated' timestamp. I was hoping there'd be some hidden customfield_123 type thing that changed but no such luck :(

For now we're using fix versions, and using that to make an assumption about if the ticket is on the board or in the backlog, but it does add risk that we miss a ticket that is in the right fix version but wasn't added to the board as there's no way to run a filter on a dashboard to catch those without manually checking.

[Yigal Lavi]

Second this, surprisingly missing functionality.

[Michal Solc]

I'd want to vote for this to be fixed as well.

The workaround for us at the moment is that we assume that non-assigned issues are in Backlog and have added an automatic rule/reminder for unassigned issues that are out of To-Do. That technically still leaves there a gap but kind of works for us, it is certainly not going to work for everyone.

[Chris (OLD Profile!)]

Looks like Atlassian is just ignoring all these missing basic features in next gen boards. Extremely disappointing and just a matter of time until companies will turn away from JIRA. Ours included.

[Jim Ryan]

Haha, I came here because the title says "Solved" but I guess for Atlassian "Solved" means "Sorry, we can't do it!"...