How to see numeric rank/order for an issue?

I want transparency around the order of an issue in the Product Backlog.

If the Product Backlog contains 134 issues, I'd like to know where a particular issue sits in that order 10/134? 27/134? 120/134?

How do I accomplish this?

2 answers

0 vote

I can't think of a way to do this in JIRA itself, I think you'd need an add-on to provide some javascript that would read the length of the current list and inject numbers into the display.

And keeping that working in JIRA Data Center would be tough!

0 vote

Actually, the question is what business advantage does having that number provide? The issues already appear in the tool in the ranked order.

Atlassian have chosen not to expose a numeric rank. In fact they got rid of it when they changed JIRA Agile to support Data Center around 6.4

As Nic says, some javascript that looks at the currently available list of issues in the backlog and adds a number to each one is one approach.

 

Yes, good point.   I can't say that I can think of much use for the number, especially it would be specific to a board at the time of running the backlog view.  As a reference, it's useless, as "#86/134 on board X" could be a different issue 10 seconds later, as could the count.  Whilst on the board in the backlog, well, I know they're in order anyway.

It is useful for Product planning to be able to understand a Product Backlog Item's order in the backlog.  Relying on only a visual indicator is insufficient when A) the list is longer than a single page or B) you wish to know the position of multiple items or C) if you wish to record the position to communicate to someone else.

If you want to compare 4 items and their position, knowing this:

Item 1: 23/134

Item 2: 18/134

Item 4: 65/134

Item 4: 83/134

is very, very helpful.

But they'll be in that order in the backlog, so I can see that.

There's no point in recording the position for someone else, as per my previous comment

I do see that it's hard to use a visual indicator when you have many issues to rank.

I think the way Atlassian intends the backlog to be used is that you keep it short (not easy) or rank the ones you care about to the top of the backlog and ignore the others for now. They might reason that you only care about some small number of Stories

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,316 views 14 20
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot