Issues in the backlog can be ranked higher (more important) than issues in the current sprint

This is covered here https://jira.atlassian.com/browse/GHS-6911 but hasn't had any attention yet. It seems seriously broken for a scrum tool to allow issues that are in the product backlog to be ranked more important than issues that are in the current sprint. Because you can't sort on the Sprint field it makes it impossible to view issues in the navigator ordered by rank with everything in the current sprint listed before the backlog.

Does anyone have a work around for this?

2 answers

1 accepted

This widget could not be displayed.

It looks like this is a known issue that doesn't seem to have much traction for change. https://jira.atlassian.com/browse/GHS-6911

This widget could not be displayed.

Frankly, you should not worried anymore about the stories which are ongoing in a sprint, it is already committed and being worked upon by the teams. Why don't you exclude them in the Issue Navigator? Priority does not matter anymore for them, and as a product owner you are not supposed to alter anything for those stories till sprint end.

Or just use the plan mode for your discusions. Press the keyboard shortcut 't' and the whole window will be just the list of containing issues in the right order.

There could be a variet of reasons for wanting to create this view in the navigator. In my case, it is for executives. We want to give them a link that will show them the complete backlog for a project in prioritized order. We could use Plan mode but a saved filter reduces confusion and user error. Executives often don't have patience for learning new tools.

But regardless, if Greenhopper can render the issues in the correct order then the navigator should be able to do it as well. And rank should reflect overall priority, IMO.

Yeah, that makes sense.

Till that bug report gets corrected, you can keep a dummy issue at the top of the Plan view and do the planning of tasks always below that issue (Kind of a marker). And while planning the sprint, keep it as the first item just below the last item being planned for that sprint.

And for executives, in the filter JQL, also add issuekey != key_of_dummy issue. Does that help?

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Thursday in United States

Local Atlassian Research Workshop opportunity on Sep. 28th

We're looking for participants for another workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sh...

46 views 0 0
View post

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you