-
Suggestion
-
Resolution: Unresolved
-
857
-
8
-
As a Product Owner, displayimg a human-readable rank (1, 2, 3, etc.) on the cards in the backlog would make prioritizing stories easier. This especially applies to larger backlogs.
Use case:
When we're ranking large numbers of new stories with the our customer in a planning meeting, we need to be able to quickly place these stories in the Top 20, Bottom 20, etc. Having a human readable number that reflected the stories position on the backlog would help with this. At present, we have to count these groupings by hand.
- is duplicated by
-
- Closed
- is related to
-
- Gathering Interest
- relates to
-
- Closed
- was cloned as
-
- Closed
- mentioned in
-
Page Failed to load
[JRACLOUD-87405] Display human-readable the rank on the card in the backlog.
+1
Hello, we need such a function.
The ticket was created in 2017 and not solved yet in 2025.
We depend on rank when planning refinement sessions as well as in BRP when knowing how to move work around. The amount of work in miro done by scrum leads to add this info (that is often changing) is wild! This is a MUST NEED field.
Our organization would find this request very valuable. Voted and watching.
+1
We depend on rank on the board for our planning and a human readable field is desirable.
Also a mention in the history that the rank has moved from 10/134 to 51/134 would be a great addition.
thank you for that @rbonus. Finally they create a ranking field. Im checking it out right now!
Advanced Roadmaps (Jira Premium & Jira Enterprise) hat this feature: Please look at https://www.atlassian.com/software/jira/guides/advanced-roadmaps/overview#how-to-get-started
+1
On my side I use a board with swimlanes and issues with subtasks have more priority or are displayed before the ones without subtasks and I need to check the list on the backlog to know the real priority. With a rank field on the board or the issue detail page it would be better.
"jsw-s7 timeout-suggestion-bulk-close timeout-suggestion-bulk-close202106"
Are you serious?
As an extension to this request it would also be helpful to know the rank of an issue when we filter, for instance if we are on a kanban board and look at the work assigned to a particular person (so filter on that person alone), it would be useful to know in which rank is a given ticket.
The same in our GmbH group, this requirement would also be very important for our Scrum Master.
I'm a Product Ops Manager at Instacart and we very much need a human-readable rank field. I agree with other commenters that this seems like a very basic feature that should already exist. How about it, Atlassian? Are 370 votes from pros in the field enough to know this is worth doing?
+1 We are looking into this issue ourselves at the moment. We can tell straight away that an easier way to see rank or re-arrange rank would be preferred... for Jira Project Admins as well as Jira Instance Admins.
Would also like to show rank numbers in the Advanced Roadmaps as well.
Fernando Gil, i used Jira automation rules. I have 4 rules.
1. rank cannot be less than 1 or greater than the total amount of ranked issues.
2. a second rule to handle moving an issue's rank up or down.
3. when an issues is completed, remove the rank and adjust all other ranks accordingly.
4. in my workplace we wanted to separate issues by department, so my fourth rule is to handle ranks when switching departments.
Juan Favela, can I ask you how did you do it? Was it with automation rules from Jira? Thanks a lot.
I have also created a human-readable rank with automation rules. It is functional but not practical.
To Atlassian: Can we get this done already? We have been requesting this for far too long now.
Yeah, we've done the same - we built an entire internal integration to do this for us. This feels like very basic, useful functionality.
+1
We've had to create an external tool just to handle simple ranking and re-ranking issues based on a numeric field. It would really help if this simple process was included in Jira.
This definitely is needed, if we are talking about prioritization and need the data to generate reports, review information, is easier to have a number next to the key. This would be awesome to have, please, consider this 
! I like the rank and use it to prioritize, but we also need some other options that provides a visual to the people to work with us.
we definitely need a Human readable numerical rankings for issues. please give an update on this.
So I did stumble upon a sort of a workaround for this provided you have the Structure plugin (ALM Works). In Structure, you can create columns that are derivative of other fields.
The workaround is as follows:
1) Create a structure displaying the desired issues, and sort on "Rank" ascending. This can be done in either the Insert, Filter, or Sort automations, and the "Rank" field does not need to be displayed on the structure itself.
2) Click on the + on the top-right of the structure to insert a new column, and search for "Sequential Index". This will create a numbered column ordered 1 - N based on the current sorting order.
Unfortunately, Structure columns are not exposed as fields for any automations outside of Structure itself. However, the structure can be exported to excel. If you create a field for numerical ranking, you could name the "Sequential Index" column with the field name, export the structure to excel, and then reimport that data to populate the field en masse. This could even be done via chron job using the REST API, but you're going to have to REALLY want that ranking as a number for it to be worth the effort.
I'm confused. Atlassian said "Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it" however there have been frequent and consistent comments from the community for the past several years that directly contradict this statement. At the very least, can you tell us how to make a value like "0|i0y0xr:" a readable number? How is that value even generated?
Thank you Peter Urda, I tried this and it does indeed give a work around that numbers the issues I needed and as a side bonus also allows me to drag and drop issues into a different ranking (fyi The Kanban board I added to the plan is ordered by rank)
Possible workaround is to add the Board to a Plan/Roadmap, limit the view to the story level. That view shows readable human rankings there; and depending on the View setup ranking changes are applied in the Plan view.
This is exactly what I need for my current use case, especially if there was a dashboard widget that could expose the relative rank of specified stories.
Appreciate your updated status and progress regarding the JA ranking display in JIRA Server
Dear Atlassian Team,
I'm following on this items since a while, what would be a timeline for decision making and implementation? From my point of view this is a very essential feature and we need to make progress here.
This is basic functionality in other tools. Please implement. Right now, I have to manually look through the entire backlog for the "highlighted" item in order to see roughly where it is the ranking.
I truly cannot believe this is not a basic feature. Is it really so hard to substitute a rank field value in a ranked list that is not eg '1|hzvm53:000d' but something meaningful like the number 1 if it's first in that list?
Another area where Azure DevOps is better than Jira hands down. They provide numerical rank, and the ability to send an item to a specific ranked position. Why is this not available in JIRA?
Dear Atlassian Team,
I would like to join the discussion here. How can it be that customers who have been using the tool for more than 10 years have to wait again and again for basic features like a ranking system?
Since 2017, this requirement has already been open, even the reporter is now no longer there. What is the next step and when can customers expect a result?
If the further development of the tools would develop as the price developments do, then we would probably no longer have any open requirements. So please give the customers the feedback they deserve.
Please add this capability