Ranking Issues in GreenHopper

GreenHopper allows you to set up rankings for your issues to help you 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 that both have a priority of 'Major'. Using GreenHopper, you can assign one of the issues a higher ranking than the other.

Enabling Issue Ranking

Before you can rank issues in your project, you need to set up a ranking field for it. This is a custom field that is added to every issue in your project. Whenever you add or edit an issue in your project, you will be able to select a unique ranking value for it.

For information on how to set up a ranking field for your project, please see Configuring your General Project Settings.

A ranking field must be specified for each project that you wish to rank issues in. You can re-use an existing ranking field, if you wish.

Ranking Issues

To rank issues in GreenHopper,

Log into JIRA.
Select Agile > Classic in the top navigation bar. Then select Classic Planning Board from the drop-down below the project name.
Tip: The 'Project Overview' mode is ideal for ranking issues.
Enable the 'Context' toolbar, if it is not already enabled, and select the ranking field for your project from the 'Sort by' dropdown. Your issues will be ordered by rank (if you have not specified a rank for an issue, you can do so by editing the issue (click the icon), selecting a rank for the issue and saving your changes).
Error rendering macro 'excerpt-include'
No link could be created for 'GH:_dragAndDropIssues'.

Ordering your issues by dragging and dropping

User will be able to move an issue card from its current position to a new one by dragging and dropping it, just like moving real cards on a conference table during a sprint meeting. When an issue is moved, all other issues are automatically reorganised. You might find it a bit tricky to rank on a two-dimensional board but you will get used to it pretty fast.

Moving cards from one page to another

For projects with multiple pages, the user will be able to move one or more (see multi-select) cards from the current page to a new « destination » page by simply dragging the card onto the pagination. After moving them, GreenHopper will display the destination page.

Moving a card with sub-tasks

When the user moves a card that has subtasks, all its subtasks are also moved as a block. A parent card can only be dropped on another parent card. A parent card can not be dropped on a subtask and, conversely, a subtask can not be dropped on another parent card.

The ranking is only applied to the issues that have at least one "UNRELEASED" fixVersion or have no fixVersions (Unscheduled). The Ranking is project wide.

The GreenHopper ranking field is based on issues that the Project lead can see. If your security levels hides some issues from the project lead these issues will not be rankable.

"GreenHopper Limitation with "Clone Issue" of Issues WITH sub-tasks"

Since JIRA is not triggering an event on the clone issue, it is very difficult for GreenHopper to associate a default ranking to the cloned sub-tasks. The sub-tasks may be displayed away from the parent Issue. You will need to simply rerank the parent for the sub-tasks to be regrouped under the parent issue or "repair" your ranking field via your GreenHopper's project configuration (GENERAL section)

Child pages