Sort Order of Sprint in Jira Backlog

Hope Adegbemile
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 18, 2024

 

 

Hi Everyone, 

 

I am in need of support regarding of ordering Issues in Jira Backlog.

Recent I implemented a new work flow to to an existing Jira project. The workflow is given below

Screenshot 2024-10-18 154139.png

Migration of Issues like Bugs, Epic, Story, Task and Sub-Task were successfully migrated to the work flow with an active work flow scheme in place.

However I have an issue with the ordering in the backlog, which i cant seem to get my way round it after attempting several Filtering Conditions.

Screenshot 2024-10-18 154628.png

In line with the pics above, There are Sprint 1 -45,. However Sprint 5, 34, 35,36,37,38 and 7 are all close print. But this wouldnt move away from the backlog. I am been trying to reorder bring. To have At least Sprint 39 and 40 back in the backlog.

Several filtering command has been initaited, but nothing changes. Can i some assistance to resolve this issue

1.  project = P.name AND (sprint in openSprints() OR sprint in closedSprints()) ORDER BY sprint ASC, Rank ASC
2.  sprint in openSprints() OR sprint in closedSprints() ORDER BY sprint ASC, Rank ASC
3.  project = P.Name AND priority = High ORDER BY Rank ASC

4.   project = P.Name AND status != Closed ORDER BY Rank ASC

5.  project = P.Name ORDER BY Rank ASC

 


In the P.Name the project name was inserted as this only should apply to one Project

Having suggestion to resolve this from the community will be helpful

1 answer

1 accepted

2 votes
Answer accepted
Walter Buggenhout
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 19, 2024

High @Hope Adegbemile and welcome to the Community!

My guess is that changing your workflow has moved issues into statuses that are (or were) not considered as closed statuses in your new workflow and associated scrum board.

For issues to be considered done in a scrum board, they must be in the rightmost column of your board. I would start by reviewing the issues in the closed sprints you refer to and verify the issue statuses of all issues in those sprints.

So, as an example, create a search to retrieve all issues in sprint 5 and check their statuses. Have a look if there's any issues there with a status that is not mapped to the rightmost column of your current board. If you haven't already done so, make sure to adapt your board, so all statuses of your workflow are mapped correctly to board columns. If that is all sorted out, then see what happens.

For a bit more context: Jira displays sprints in the backlog based on the value of the sprint field on any issues returned by your board filter. Issues in a status that is not in the rightmost column of your board are considered incomplete and - as a result - appear in your backlog. If they are associated with a sprint, then that sprint is displayed as well.

Hope this helps!

Hope Adegbemile
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 19, 2024

Hi @Walter Buggenhout Thank you for your reply


Nailing the issue down to board really helped to resolve the issue. I finally discovered the project has 3 different  board applied. When the default board was selected everything looks to be in the right order and the backlog now has only the active sprint. Thanks for the insight

Like Walter Buggenhout likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events