Why doesn't the ranking of issues in the issue browser match the ranking of my Agile board?

Using the same filter to search as my Agile Board uses, I can't get the issues to rank in the same order as they appear in the Agile Board (planning view).

The board's filter is defined to use ORDER BY Rank ASC. Viewing the same query in issue browser, the issues appear in a completely different order. What's going on?

I'm ultimately trying to export my agile planning board into Excel for a client report. The ranking is everything.


2 answers

0 votes
Ahmad Danial Atlassian Team Sep 17, 2013

Hey there, Pierre.

When you mentioned that you display the same query in the Issue Navigator, can you please cross check whether the filter is actually configured by ORDER BY Rank ASC? You can check this by switching the Issue Navigator to the Advanced Search mode to compare the results. Sometimes, this could be the reason behind this issue.

Else if the order of ranking is still out of place, please try to perform reindexing in your instance and check again:

Hope this helps.

Warm regards,


Hi Danial,

Yes, I did verify that the filter was actually configured for ORDER BY Rank ASC, and then I performed a re-index.

It would seem that the problem might lie in that I have several sprints tentatively wrapped around the top stories and issues; when I export the data and sort it in Excel by Sprint, sub-sort by Rank, the issues appear in the right order.

Unfortunately, the Advanced Search does not let me order by Sprint, Rank; it returns an error that says that Sprint is not a field you can sort on.

Any suggestions?



I have this exact same symptom/problem: a series of tentative sprints and unable to get the issues ordered in the same order via a JQL on rank.

As do I. I have some 'fake sprints' needed to organize my 2,000 task backlog. I need my designer's dashboard filter to mimic my agile board rank and it does not. I've tried sorting by Rank and Global Rank but no luck. Both of which use a non-numeric ranking system (ex. 0|i3nsnr:) I am unfamiliar with Client Rank. 

Martin, did you ever figure this out?

We are having the same issue here. By extension our story level issues in portfolio do not match the order we have determined in JIRA. Occasionally JIRA will spaz and become reordered based on the global rank. Has anyone figured out a fix?

Are you using Client Rank ? If yes, you need to use the global Rank in JIRA. Client Rank use internal hashing which is different from numeric Ranking.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Statuspage

Introducing Statuspage Getting Started guides! First up: What is Statuspage?

Over the next several weeks we'll be sharing some of our Getting Started guides here in the community. Throughout this series of posts, we'd love to hear from customers and non-customers ab...

201 views 4 1
Join discussion

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