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?
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
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.
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
I agree that this would be a helpful tool to have, or at least the ability when viewing a single issue, to view its position in the current backlog or sprint. Working as a client representative, when I'm viewing an issue for the first time, I have to open a new tab and search for the issue in the backlog. Why not just take me there with a single click, if it needs to be a visual one. I can see in the notes that an issue has been "Ranked Higher", so there is a "rank" field somewhere.
I find the responses to repeated requests for a simple ranked number value frustrating. “I know you want it, but you don’t need it.” For me this is a deal breaker. Visualizing work is a basic Kanban principle. When looking at a single story, I want to know this is rank “17/134” without having to navigate to a backlog view.
It's not a case of not needing it. You do need to see the order.
But you'll have to do it with a relative script that is for display only, and will change by context (apparently randomly at first glance)
"Simple" numeric ranking at a global level increases the work any re-ranking work exponentially by the number of issues you have, so it really can't be done in real life.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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!
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