Documentation for GreenHopper 4.3.x . Documentation for other versions of JIRA Agile is available too.
GreenHopper is now called JIRA Agile. Learn more.

GreenHopper allows you to create master-slave relationships between versions. For example, you may wish to group your sprints as milestone versions (e.g. "Version 1 m1", "Version 1 m2", etc) under the version for the major release (e.g. "Version 1"). In GreenHopper, you can set up the major version as the "master" version for the milestone versions. This allows you to view and track all of the issues assigned to the milestone releases under the umbrella of the major release.

Which fix version do I see on the cards/summaries?

The version displayed in the summaries and cards is the committed version. If you are using a 'Master' version, the committed version will be the end-child version where your issue resides. Otherwise, it is simply the version where your issue resides.

To set a version as the master of another version,

  1. Log into JIRA.
  2. Click the 'Agile' menu in the top navigation bar and select 'Planning Board' from the dropdown that displays. The 'Planning Board' will display.
  3. Select your project from the project dropdown in the top navigation bar, if it is not already selected.
  4. Change the viewing mode to 'Version' mode.
  5. Locate the box for the version that you want to be the child version in the right-hand column.
  6. Edit the 'Master' field by clicking the icon which will appear when you hover over the field.
  7. Select the version that you want to be the master version from the dropdown. The Planning Board will refresh and display your version under its new master version (see screenshot below). The child version will also have an icon display in its header.

Screenshot: A master and child version in GreenHopper

  • No labels





Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.