ISSUE ACTIONS

Planning Board

Task Board

Chart Board

Useful Links

JIRA Links

INTRODUCTION ...

Back to top

1. Issue Create

From most GreenHopper boards you will be able to create issues or sub-issues via the "New Card" button and the "+" icon within the issue views. You will first be presented with the issue type selection (of course you can add your own via the JIRA configuration) then with the new issue card that will be based on your issue type template.
For some reason you may want to lock the possibility to create issues via GreenHopper.
This is possible via the "Card Creation" setting in the general setup of the configuration.

"Create" will create the issue without closing the modal screen for another quick issue creation.
"Create and Close" will create the issue and will reload the Board focused on the newly created issue.

Back to top

2. Issue Scheduling

Managing your issues between versions, components or even assignees has actually become a fun task in JIRA with GreenHopper.
By a simple drag and drop you can associate your issues to a fixVersion, component or an assignable user (see Planning Modes)

Dropping an issue card into the desired version/component/assignees box will automatically update the issue version/component/assignable user. Your box statistics will of ourse be refreshed.

Since the multi-selection is enabled in the planning board (Alt + left click or Atl + left click), to update your selected issues, just drag and drop them into the desired version/component box.

If you are updating a task containing sub-tasks, GreenHopper will automatically ask you if you wish to update the sub-tasks as well. You will be able to choose the ones to update and the ones not to. Note that the sub-tasks in the same version of the parent will be selected automatically.

Back to top

3. Issue Ordering

Enable issue ordering (prioritization)

Create a GreenHopper Ranking type custom field for each prioritization needed from the Custom field administration panel.
The new GreenHopper Ranking type ensures complete integration with JIRA.

The Number Searcher must be selected as the Search Template
The Custom field needs to be associated to "ANY ISSUE TYPES"
Select only the projects that will use this field

Register your GreenHopper ranking field for each project that is subject to use it from your project`s planning board configuration (in the General section)
You can register more then one GreenHopper ranking field.

To start ordering
Simply select your GreenHopper ranking field in the Sort by combo from your context menu

Drag an issue on another issue.
User will be able to move an issue card from it's current position to a new one. Just like moving real cards on a conference table during a sprint meeting. When an issue is moved, all other issues are automatically reorganized. You might find it a bit tricky to rank on a 2 dimensional board but you will get use to it pretty fast.

Moving one or more 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 Subtasks
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 Porject 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)

Back to top