-
Suggestion
-
Resolution: Unresolved
-
804
-
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.
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.
I've wanted this for years and hoped we would have it now. Please Atlassian, move this up the queue!
As a product manager with multiple, large backlogs I would so love this simple feature. Please Atlassian!
May not help everybody here, but I created a "Prioritized Rank" field with automation that solves the use case for my company. I wrote up a community post about it in case it will help anyone else!
@Ben Schröter As a workaround for a weekly meeting it may help to export the board to Excel with the rank and sort by rank, then you have the row number. Of course this won't work if you need to edit on the fly during the meeting.
@Abbey Eastman, we don't have that field. Perhaps it is a custom field. But if you are entering a numeric priority there, this won't work for us because we have a lot of churn, i.e. where more urgent items come in and either get done or de-prioritised, etc.
I already commented more than a year ago that this is an essential feature. Every week during our stand-ups we guess about the position of the items based on the scrollbar position. this is everything but efficient work...
Would be great to hear a comment from Atlassian on what are the plans for this very much wanted feature!
Our team is currently using 'backlog priority' to help "rank" the order of the Jira tickets on our boards. This too is a manual process, but it is a numerical field that may help in the meantime. You can find it when you are in the ticket and click on Edit. It will be displayed with the list of items to include the Epic, Label, etc.
It's been 11 months since I first commented on this issue that should not have been closed. It would be nice if it moved from Under Consideration to In Progress, or some communication could be made on the matter.
Would be extremely valuable, as our Jira requestors need to know the relative order of their request to manage expectation, and without this human-readable rank, I don't know how we can relay this information to them efficiently.
Using Jira Plans, and if I sort by another field then I lose all visibility of the rank ordering. So I'm unable to access this data unless I have two versions of the window open side by side. Having a numerical value to show this would be very valuable.
I agree that this is a required feature. As a company we migrated to the Atlassian stack a few years ago & before that we used FogBugz instead of Jira - this is the one key feature that we miss from FogBugz. As everyone else is saying- it is essential for the efficient management of a backlog.
I am fairly new to Jira but this feature seems like a given - please make the ranking readable to humans, in numerical. I beg of the team. This is absolutely necessary managing multiple projects and a large backlog.
I also cant believe that something so small takes 5 years in the making. I also miss this feature totally as I have about 500 issues in the backlog with 50 people working on it and I need to know where the issue is located to know its priority. Why does that take so long?
This feature is necessary for our customer to have another possibility to prioritze projects for further plannings.
Pls implement this asap and also for Server / Data Center pls.
Best
Tobias
This is a must when managing a large backlog and multiple projects across multiple boards. Please Implement this!
We're 5 years in and...? I know it goes by 'votes' but... sigh.
Ranking items across multiple BUs. Being able to view this information allows the project/program managers an easy way to have multi group discussions.
Please. If there's a field that is used in Jira that users can manipulate, make it so users can read and understand it.
Hi dear all,
As was mentioned in the issue:
https://jira.atlassian.com/browse/JSWSERVER-15444
We also have a datacenter, not a cloud, if any of you has the same case, would you please add a comment?
cheers!
This would help us to achieve the Architectural Runway technical sequence we need
Good day, would like to extract our Jira data into a BI system and plot the ranking against lead time. Higher rank should have lower lead time, etc.
This is a must have feature. Agile is dynamic in nature. A story that is priority today can be de-prioritized at a later stage. Going through the titles makes it cumbersome to locate the user story in a large stack. Same functionality exists in ADO tool also. I am not sure why such an important and small field goes missing in JIRA.
Advantages of having this field in backlog.
- Sequencing of user story for dev team to pick on priorty.
- Helps in showcasing to audience about the logic being build for a feature.
- User doesn't have to go and read each and every title to locate a specific US, if the rank is mentioned they can directly pinpoint the intended US from stack based on business logic written in US. A login story will always stay top and logout at bottom.
Dear @mhunter do you know whether we would have any news from this feature?
I agree that this would be much appreciated, as the alpha numeric indicator is very confusing to teams and customers.
This would be a huge win for us as well. Please prioritize this VERY HIGH on your backlog. It would be incredibly valuable to see the rank displayed.
This is a must have. Otherwise prioritising huge backlogs is super challenging for us.
This would be a powerful and very friendly feature, we are looking for a way to implement it
Would really help us as we could avoid using a naming convention to indicate the priority order of issues. Have voted for this.
This seems like an essential feature to me... Today if you want to see the ranking of a specific story you would have to open the backlog and count... Seeing the ranking as an attribute of the story is really helpful for teams to work according to priorities! Or you have to add an additional "priority" attribute that is redundant with the ranking in the backlog and might lead to confusion...
Unfortunately, commercial interests take precedence over customer needs.
I'm just curious as I haven't ever followed an feature request before. Has anyone ever seen one of these popular requests implemented by Atlassian before? I've heard that these generally just get closed and ignored, but that is just anecdotal feedback from the office.
I agree with AJ Otto. Please don't close this! If your technical team are saying it's too difficult, as they were implying last year, bring some other expertise on board - there is always a workable solution, even if it's not the full ideal one.
Agree with all of the above - competitors have this feature and it is such an easy add and would have tremendous value. Agree it should also be part of the export.
Would be such a useful feature for us. We have specific meetings looking at the top X issues and it would be so useful to see the numeric rank of an issue to know if its above or below the line for consideration.
Please add this functionality. It would also be helpful if ranking could be linked to teams. An issue could be 1/100 for the over all project but 2/10 for a specific team.
This would be a really helpful feature. Also, if the human readable rank value had clear representation when exporting issue reports (i.e. to CSV), that would be a plus!
Thanks!
Please add this feature. We just moved from Trello, and missing it in Jira is quite frustrating. Thanks
+1!!