Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Which field to use ranking Jira issues with multiple filters?

This is my filter query:

assignee in (currentUser()) AND project = GJP AND issuetype in standardIssueTypes() AND status in ("In Review", Pending, Reopened, TODO, "Work in progress") AND labels in ("Default", Learning, Regular, Support, Transcation, Trending) ORDER BY due ASC, priority DESC


So, according to above query, 10 issues are coming in the list. 5 out of 10, which is coming on top of list and matching with ORDER BY. Because Due date and Priority are same for all 5 issues.


Now, my question: Out of 5 which has everything same [due date and priority], I want one more field, which even give more priority-ranking, and should indicate that that which one to complete first. like for example  for all 5 issues, I want to give number 1,2,3,4,5. So that first I can complete number 1 issue, then 2 and so on...!


Can you please advise what should I do for that?

1 answer

1 accepted

2 votes
Answer accepted

Hi @Jimmy Trivedi 

You could use Rank ASC?

Rank ASC will order the Issues as they appear in your Board/Backlog, from highest to lowest. If the Issues are already in order on your Board - that could be a simple solution.

So your JQL might look like...

...ORDER BY due ASC, priority DESC, Rank ASC

I'd be careful with using number fields for prioritisation. These can get complicated - for example if you had 100 issues numbered 1-100, and then needed to add an Issue at 62, there's lots of other Issues you'd also need to edit!

To see more information about how Rank works across your wider Jira instance - see this help page:


Hi Thanks for the reply, but I'm not able to modify it, please check 3 screenshot.Screenshot 2023-01-22 at 19.23.12.pngScreenshot 2023-01-22 at 19.24.53.pngScreenshot 2023-01-22 at 19.25.12.png

The ranking is used in the backlog to do the click and drag to rearrange the order of the issues in your backlog. 

You can not edit it directly, because Jira can't risk a human entering a duplicate value.  It's generally not even displayed to us because it is not a human-friendly format.

Nevertheless, ranking is the best way to do what you want.  The way I think of it is that "priority is a great piece of information to inform ranking, but it can not dictate it"

Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events