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

Top N ranked issues per reporter

We are telling our reporters to Rank their own issues. For this we use the standard Rank functionality in a board filtered on their own issues. I would like to create an overview of the Top 5 issues per reporter, based on Rank.

Sorting by Rank is not an issue, but I cant seem to find a way to Limit results, let alone per reporter. 

Any suggestions?


I was considering setting up a secondary field + workflow which would hold a Rank (int) value based on the COUNT(issues with a numerical lower rank) +1 
I cant find a way to filter issues based on rank against the rank of the to be updated issue.

3 answers

1 accepted

We decided to go with the Priority DESC + RANK ASC. 
Priority highest and high are good preselections where the RANK has limited value.

Not exactly what we want, but yeah. 

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 08, 2023

I think there may be a way to do this, but I think it's going to be clunky.

The first one would be to have a flag field for "in someone's top five", which you'd need to maintain somehow.  Obviously, doing this by hand would not be a lot of fun.

I'm not sure an automation could do it - as they re-rank their issues, remove the flag from anything that ends up in place 6 or below and add it for anything in 1-5.

Priority might be easier to work with - give them a scheme with 5 priorities, and automate something that means that they can't set an issue to have a priority that another one of their issues already has.

However you do it, you'd then do your team ranking in a Kanban board who's filter includes "and priority is not empty (or lower than the top 5)" or "and top-flag is set"

0 votes
Hannes Obweger - JXL for Jira
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
May 08, 2023

Hi @Steven Waltman

just thinking out of the box: Is it really so much about limiting the amount of issues, or is it more a matter of presenting the issues "by" reporter, i.e., in groups of issues for every reporter? 

Reason I'm asking is that I can't really think of an easy to limit the number of issues (although you could probably "count" them somehow using Jira Automation and write the result into a custom field, and then query by this field) - but there's definitively ways to group your issues by reporter ... and if this grouping is presented nicely, I wonder if it really has to be exactly 5 issues per reporter. But this really depends on your exact use case, of course.

Happy to elaborate further if this sounds like a way forward,



Hi Hannes,

Thank you for your answer.

I see I didnt fully explain my usecase, apologies for this.

We ask each reporter to come up with their 'top 10 (unresolved) issues'. The bundling of issues per reporter and have them sort this is easily enough in a Kanban board with data grouped per reporter. They sort a their own tickets.

Second phase is we sit down as a Team, and look at the complete picture of what is 'top'. Here the issues are no longer grouper per reporter. As we have a small team we want to understand each others top priorities and discuss what we think as a team is the true top priority and sort accordingly. 

The complete picture however contains hundreds of issues, not 5 (reporters) x 10 (issues)

This list is sorted based on the Global RANK, which was affected with the Reporters sorting their tickets. This however doesn't place these 50 issues in the top 50. As during sorting we reporter John might have tickets starting with Global Rank 250 and report Jane might start at Global Rank 10. Which is expected behaviour.

Of course we could switch to using the 'priority' field for this. Everybody can have 10 'prio:highest' tickets, but I aim to have the drag&drop + automation as enough to get to the desired outcome.

Kind regards

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events