Currently my rank field is populated with odd combinations of alpha and numeric characters. For example, the top five items in a backlog (in descending order) are:
I also have to agree with Janet and Mandy - the very simple real world use of a numeric 1-2-3-4 would GREATLY help me in communicating the backlog to people. Please update me when you add back the feature to have a common language rank. It is the number 0|r90tqx: feature for you guys to add.
Could you please explain why Lexorank is better? I've never found 1, 2, 3 to be unreliable or fail to work.
My team is doing software development, and our backlog would normally be 1, 2, 3,... We don't need other functionality, and would like to be able to tell what a column of numbers means. This just looks like gibberish:
When I searched for information on LexoRank, I didn't find an explanation, but I did find a bug: https://jira.atlassian.com/browse/GHS-11358
Well, the major improvement in JIRA Agile which came with the lexorank is the possibility to work in a clustered and database agnostic environment. You can found further information about this in https://extranet.atlassian.com/display/GHDEV/LexoRank+%3A+A+Cluster-Safe+Ranking+System You may also be interested in the discussion in https://jira.atlassian.com/browse/GHS-10748
The newer version of JIRA Agile does not rank issues using a number, but a lexical value, using the lexorank algorithm. So, if you are facing this issue after upgrade JIRA Agile, I do not think you will be able to use numerical values again to rank your issues.
The Lexorank algorithm has a lot of advantages when compared with the numerical rank, as being more reliable and work in data-center enviroment.
I'd have to agree with Janet. When looking at an issue in any detail screen, you have no way of knowing where the issue falls in priority on the backlog. I don't want to have to keep switching back to the backlog view to know where the item has been ranked. I'm sure the algorithm is fine, but I need an equivalent numeric value for when items are in detail screens to provide context that is human understandable. Thank you.
Not to pile on but my company is having a very similar issue and i believe Janet is exactly correct. I am well aware of the advantages of the Lexorank algorithm but most of those are behind the scenes; there must be a front facing value that makes sense to humans. There are a number of reasons why users would need to see the rank value outside of the Agile Board Planning view. They are displaying in the correct order, it cannot be that difficult to assign an ascending value starting at the first entry. Please help!
Teilor, your comments above have links that give me a 404:
Do I need another login?
This ticket does appear to be a duplicate of https://jira.atlassian.com/browse/GHS-10748
Sorry Janet, I didn't notice the access to that document was restricted; you will not be able to view it. If the change from the numerical rank to lexorank cause a negative impact in your JIRA instance I would recommend to you to create a Suggestion to our developers in https://jira.atlassian.com, with details about your user case. We also have a Support channel in support.atlassian.com
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot