Ranking an Issue

Ranking an issue alters its relative priority within its current column and swimlane. Ranking your issues helps you to organise tasks in your product/sprint backlog more effectively.

Rankings allow you to prioritise issues at a more granular level than issue priorities in JIRA, as rankings can help you to determine whether a single issue is more important/urgent than another single issue. For example, you may have two separate issues which both have a priority of 'Major'. Using GreenHopper ranking, you can assign one of the issues a higher ranking than the other.

Plan mode is only available for Scrum boards.

To rank an issue in Plan mode:

1. Click the Agile link's down-arrow in the top navigation bar, then select your preferred board from the resulting dropdown menu.

2. Click Plan to go to Plan mode.
3. Rank an issue by dragging and dropping it to a higher or lower position in the backlog (see Screenshot 1 below);
   or:
   (In GreenHopper 6.1.2 and later versions) Send multiple issues to the top or bottom of the backlog by selecting them (Shift>Click or Ctrl>Click) and right-clicking (see Screenshot 2 below).

To rank an issue in Work mode:

1. Click the Agile link's down-arrow in the top navigation bar, then select your preferred board from the resulting dropdown menu.

2. Click Work to go to Work mode.
3. Rank an issue by dragging and dropping it to a higher or lower position within its current column (see Screenshot 3 below).
   If an issue has sub-tasks that are in the same column and swimlane as itself, the sub-tasks will be shown in a group below the issue.
   
   • When you rank an issue that has sub-tasks, all of the sub-tasks that are currently grouped with that issue will be automatically moved with it.
   • Sub-task issues can only be ranked in relation to their 'sibling' issues.