Rank association to boards

We're using JIRA cloud, and have several different boards using a common filter query. All of the boards have Ranking enabled. 

Noticed recently that changing Rank of an issue on one board causes the Rank to change for the same issue on a different board. 

Previously I worked on JIRA Server (v6?), and I vaguely recall that Rank was specific to the board. In other words, same issues, different Rank dependent on what board you were on. 

Is that not the case with cloud? What is the Rank handling across boards, across filter queries, or across what?

Thanks for any insight that can be provided. 


1 answer

1 accepted

0 votes
Accepted answer

I think your memory may be wrong.  Rank is a global field, and it ranks every issue against every other issue, irrespective of type, project, board etc.

Certainly possible that my memory is incorrect on this. I just remember looking at server schema back then, and seeing board IDs associated with rank data. Again, this could have been old obsolete or deprecated functionality even at that time. 

Also, the Rank data at the time was not integer-based. It was alpha-numeric in nature.

When "Software" was "Greenhopper", there was an association, but that's before v6!

probably what I'm thinking of. 

Is there a way to associate a Rank with a single board, and not have changes to the Rank elsewhere affect it on that single board? I see this explanation of having "multiple fields of type Global Rank", and wondering if there is some way to implement that from the client-side? 


You can try adding multiple rank fields, but it tends to be a complete disaster, as each field makes a nonsense of the others.

It's no real sense to have boards ranked differently as well.  If one issue is more important than another, why should it appear differently on different boards?

Good question! 

One use-case has to do with dueling product managers. You have multiple epics, for which a product manager may have purview over some; a different product manager has purview over others. Each product manager has their own board. Each PM wants to see all his stuff up at the top, because they can't filter for multiple epics at a time. 

Another use-case would be multiple teams working on the same project, each with a separate team board. Same essential problem - the scrum master of each team wants to order all their team's items up to the top in a variety of fashions. 

There are probably different ways you can get to this - through filters, labels, custom fields, etc. But in the end, it would be so much easier if there was a board-specific Rank.

Global ranking forces product managers to co-operate (or just look stupid - their choice)

Boards don't have to include everything.  If a PM doesn't care about a set of issues because it's not their project, don't include them on their boards.  Then the global ranking relative to the stuff the do care about is irrelevant, as they don't see it.

There is no problem here, just use the global ranking to indicate actual real life importance of everything, and then let the boards focus on each PM's area, excluding the stuff in other areas.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

936 views 3 9
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