JIRA Agile 6.4.4 messed up the ranking

Hi all,

we just upgraded to JIRA Agile 6.4.4 and according to the upgrade notes https://confluence.atlassian.com/display/AGILE/JIRA+Agile+6.4+Upgrade+NotesAtlassian introduced a new alphanumeric "Rank" custom field.

However, with those values the order of the issues in all our agile boards are messed up. Since we use Ranking, all board queries use the "order by Rank ASC" in the end, but the new values mess up the entire ranking.

Are there new order by functions that I can use to obtain the previous order?

It seems that I cannot even use the old field anymore, because according to the atlassian documentation:

If you use the Rank (Obsolete) field in a filter for a board, then ranking will be disabled for the board.

@Atlassian: Why do you introduce a new ranking model and don't map the old values correctly to the new ones, so that the order of the issues stays the same?

1 answer

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,774 views 18 21
Read article

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