nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why so many issues in backlog?

Jirong Hu

I've migrated thousands of issues from Rally to JIRA, now seeing many in the JIRA backlog.

I see the backlog query is showing like this:

project = CVE AND status in ("10100", "3", "11600", "10002", "11603") AND (cf[10004] is EMPTY OR cf[10004] not in openSprints()) AND issuetype in standardIssueTypes() AND issuetype != "10000" AND NOT status in ("11600") ORDER BY Rank ASC

From https://rbcjira.devfg.rbc.com/rest/api/2/field, I see cf[10004] is Sprint. How can I find out what's the name for the ids in the status?

Accepted answers

All comments

Nic Brough -Adaptavist-

That's quite a complex query, and if it is viewing "too many" issues on the board, I would say there is something not quite right with the OR parts.

Decompose it, and try to simplify. Do you really mean

All issues where the Project is CVE where status is in (list) and Sprint is empty
And
All the issues where Sprint is closed and the issues are story level and of type X and they're not in a certain status

My best guess is that the second clause is grabbing vast swathes of issues from other projects.

I would simplify:

Generally, a board does not exclude most of that. You want to select all status, otherwise you will miss stuff. Although you can tell your board to simply not have certain status included in a column, so it won't show, that's quite counter-intuitive
You don't want open sprints only on a board, or you won't be able to plan
You shouldn't be worrying about issue type so much. Issue is of a few types, maybe, but I wouldn't bother with excluding sub-tasks in the board filter, the board understands they're not stories and they can be useful in a sprint, so instead think of hiding them later, giving you a more generally useful board

I would use

"Project = CVE" as the board filter
Possibly a clause for issue type (leaving sub-tasks on the board)
If I was certain there were status that should not happen in my sprint, then I would first drop them from the board by removing them from the columns they were in, and then think about amending my workflow so it simply no longer uses them
Have a "quick filter" on the board for "issueType is not in subtaskTypes()" - this enables you to quickly toggle their display on and off

Jirong Hu

Hi Nic

Thank you so much for the detailed explain. I think I missed something here.

See the attached screenshot. I simply access the Backlog from the menu left. The query was showing when I click the icon looks like a CPU. I was assuming the backlog is generated by a fix query in JIRA, but seems like the query is generated by looking at issues in Backlog (the other way round)?

Nic Brough -Adaptavist-

The backlog is

Everything selected by the board filter
Minus done issues
Minus sub-tasks
Minus things in an active sprint

The backlog absolutely is generated by the board filter, not the other way around. Your filter is complex and long.

Can you try going to "board configuration" to see what we're really looking at? Should be some ellipses (...) near the top right

Jirong Hu

Is this what you are looking for? The filter query is project = CVE ORDER BY Rank ASC

I mean I didn't create that complex query. That query shows when I click the "CPU like" icon.

Jamie Echlin _ScriptRunner - The Adaptavist Group_

That query is generated by jira. The contents of the query is nothing to do with us. We're just surfacing it so that you can view the backlog issues in the issue navigator. That is the actual query jira is using to show the issues in the backlog on the planning board.

> The weird thing is when I look at our JIRA PROD server, the query for Backlog is simple as:

project = CVE and sprint is empty ORDER BY Rank ASC

You must have an older version of SR4Jira, this was changed as part of https://productsupport.adaptavist.com/browse/SRJIRA-3954?jql=project%20%3D%20SRJIRA%20and%20text%20~%20%22backlog%20query%22.

Although now I look I see there is a follow-up and a new issue: https://productsupport.adaptavist.com/browse/SRJIRA-3366. I haven't properly investigated that yet.

Either way, check the version of the plugin you have and see if either are before 5.6.8.

Jirong Hu

Hi Jamie

Thanks for your time to looking into this!

I think I am hitting a similar issue, but I still don't know how to fix it. The version is 5.6.11.2-p5 as shown below.

Jirong Hu

Current SR version in our JIRA PROD is v5.4.12, where I don't see the issue (but I haven't import my data yet).

Not sure if the problem in our JIRA DEV server is created by my import is my real concern.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server