GreenHopper Synchronizer lets you automatically synchronize GreenHopper Rank with the position of issues in the structure, and Epic/Theme field with the position of stories under epics in the structure. |
GreenHopper synchronizer is available only for JIRA 4.2 or later and only when GreenHopper plugin is installed. |
GreenHopper 5.8 introduced Global Rank field, which can be used to manage a multi-project backlog. GreenHopper synchronizer in Structure lets you select multiple projects to sync with when you are using Global Rank. |
Project |
A project that GreenHopper is used in. The structure may contain issues from other projects, they will not be affected. |
|
Auto-add Subtasks |
When turned on, sub-tasks will be automatically added to the structure and forced to stay under their respective parent issues, like they do on GreenHopper's Planning Board. This works similarly to Sub-Tasks Synchronizer. |
|
Rank Field |
The field of type "GreenHopper Rank" that holds the rank (backlog order) for the selected Project. If you do not wish to synchronize rank, select Don't synchronize. |
|
Epic Field |
The field of type "Labels" that is used to hold the key of the Epic that the story belongs to. Typically named "Epic/Theme". If you do not wish to synchronize Epics content, select Don't synchronize.
|
|
Epic Type |
Relevant only if an Epic Field is selected. Defines an issue type that is treated as Epic - typically named "Epic". All issues placed under an issue of this type in the structure will be updated to have Epic Field point to that issue. |
This synchronizer supports both Import and Export / Resync into/from Structure (more about resync). Incremental synchronization watches both structure changes and GreenHopper changes and applies the change to the other side.
CAREFUL! Please be careful when using this synchronizer, especially when you add multiple issues to the Structure, as this may lead to massive updates in the GreenHopper ranks without undo. |
Common Rules:
Sub-Tasks Synchronization:
Rank Synchronization:
This restricts the possible rank changes in GreenHopper - you can only move an issue to the position of another issue that is under the same parent issue in the structure, otherwise the issue will "jump back" later. |
Epic Synchronization:
When GreenHopper synchronizer is enabled, it automatically updates GreenHopper order in background when any Structure change happens. So if you carelessly add issues from the sync'ed project to the structure in some random order, their ranks will be updated according to that order.
To add issues to the structure without breaking the existing backlog order:
GreenHopper's Planning Board is flat (except for sub-tasks), and the Structure is hierarchical - so it is not possible to precisely rearrange Structure to have all issues come in the same order as they do on the Planning Board, without changing issue parents or making the Structure also flat.
Henceforth, the Structure syncs subsets of the issues in the hierarchy with GreenHopper rank. For example, consider the following Structure:
A |
|
|
B |
|
C |
D |
|
|
E |
|
F |
It is not possible to rearrange the sub-issues so that they come in the following order: B, E, C, F - although this is possible on the Planning Board. Instead, the structure will synchronize sub-sets of the issues in the Structure with GreenHopper. The following sub-sets will be synchronized separately: