How are components ranked internally?

We have a number of Projects in Jira where one of them is for internal support from all departments in company. At the moment we have 11 components in this project where each component belongs to a department. At the moment we have around 300 open issues in project in total.

Each department prioritize their issues by drag-and-drop on the planning board for all issues in their component.

We would like the ranking in components to reflect the ranking for all unscheduled issues. Here is a simple example where there are 2 components with 3 ranked issues in each. Today the unscheduled queue (overall) looks like this:

1. Component1 Issue1

2. Component1 Issue2

3. Component1 Issue3

4. Component2 Issue1

5. Component2 Issue2

6. Component2 Issue3

We would like the overall ranking in unscheduled queue to be like this:

1. Component1 Issue1

2. Component2 Issue1

3. Component1 Issue2

4. Component2 Issue2

5. Component1 Issue3

6. Component2 Issue3

Is this possible and what determines the internal ranking between components?

Also sometimes new issues appear on the first page in the unscheduled queue as if they were already ranked. They should pr. default appear in bottom (last page) no matter if they have component added.

I haven't been able to find any documentation about this.

best regards


2 answers

1 accepted

Hi Casper,

This partly depends on what version of GreenHopper you're using. In recent versions (past 5.8.x) all issues in the entire system participate in a Global Rank (i.e. all issues are kept in a list ordered by rank). Any issue can be ranked against any other by dragging and dropping on the Rapid Board (or planning board). There is no special ranking applied to components, new issues that are added simply automatically go to the end of the list of ranked items.

You can change the order by dragging and dropping the items to be in the order you wish them to appear.



To tell you the truth it is not clear enough how the "ranking" should work. Not sure if any ranking in components exist (seems to me that not), why not to consider basic Priority option?..or some customfield which could be used for ranking and set manually by mananer?...

Suggest an answer

Log in or Join to answer
Community showcase
Jason Wong
Published yesterday in Agility Beta

Welcome to agility

Every team in the world is unique, and so   Atlassian believes   that each and every team's best way of working  needs to  be molded to their unique circumstances  – ...

333 views 6 15
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot