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; } } }

backlog order with new issues created

Kevin Wu5

When you create a new issue and then try to see that issue in the backlog, it appears that the issue is inserted somewhere in the middle of the backlog order.

Is there a way to configure the default order of newly created issues? Either at the beginning or at the end?

Accepted answers

Tarun Sapra

Currently it's an feature request in JIRA

https://jira.atlassian.com/browse/JSW-11139

https://jira.atlassian.com/browse/JSW-5368

All comments

Tarun Sapra

Currently it's an feature request in JIRA

https://jira.atlassian.com/browse/JSW-11139

https://jira.atlassian.com/browse/JSW-5368

Joe_Kirschling

I have a similar issue... when a sprint is closed with existing PBIs that are not DONE, the incomplete PBIs are randomly placed in the backlog with no apparent rhyme or reason... since these are current issues that will likely be pulled into the next sprint to complete they should be placed at the top of the backlog.

Are the above tickets likely to resolve this issue as well or do you think I should open a separate request?

Also, there has been no recent activity on those tickets... I feel like this is a common, highly visible problem that should be resolved sooner than later.. what can be done to raise visibility of these issues?

Joe_Kirschling

Trying to figure this out... found:

https://jira.atlassian.com/browse/JSWSERVER-7579

Says items are added back to backlog in order of 'rank'

This sounds good, but in practice it doesn't work well.

The items placed in an active sprint should be defacto the highest rank regardless of where they were pulled from. Moving an item from the backlog to an active sprint is (or should be) a 'ranking' action.

The backlog is groomed and re-ordered while the sprint is in progress and those items in the active sprint are excluded from this ranking (for obvious reasons), so when the unfinished items return to the backlog they are bumped lower into random spots and are hard to find.

It seems like they changed this from incomplete items being placed at the top of the backlog in previous versions for some reason..

I'm not really sure what to do about locating these stray issues.

Monika Gottwald

We have the same problem here. To workaround the problem with completing sprints we create a new sprint before we complete the current sprint. Then there is a possibility to send the incomplete issues to the next empty sprint.

William Bardallis_sq9zgz

Jira has been around for a long time and should follow Agile/Scrum standards. New issues should go to the bottom of the backlog until the Groom/Planning cycles. Then you drag it where it belongs/prioritize/estimate/etc.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-core