Search the GreenHopper 5.8.x Documentation:

Index
Downloads (PDF, HTML & XML formats)
Other versions

This documentation relates to GreenHopper 5.8.x.
If you are using an earlier version, please view the previous versions of the GreenHopper documentation and select the relevant version.
Skip to end of metadata
Go to start of metadata
GreenHopper allows you to create parent-child 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 "parent" 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.

All issues under the child version are considered to be a subset of the parent version. These version hierarchies are useful for managing Releases/Sprints/Teams. For example, if you set 'Version 2' to be the master of 'Version 2 milestone 1', then you will be able to view all the issues assigned to 'Version 2 milestone 1' when you view 'Version 2' on the Planning Board.

Which fix version do I see on the cards?

The version displayed in the summaries and cards is the committed version. If you are using a 'Parent' 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 parent of another version,

  1. Log into JIRA.
    (info) You will need to have the JIRA 'Project Administrator' permission in the relevant project.
  2. Click the 'Agile' link's down-arrow in the top navigation bar and select 'Planning Board' from the resulting dropdown menu. The 'Planning Board' will be displayed.
  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 'Parent' field by clicking the icon which will appear when you hover over the field.
  7. Select the version that you want to be the parent version from the dropdown. The Planning Board will refresh and display your version under its new parent version (see screenshot below). The child version will also have an icon display in its header.

Screenshot: A parent and child version in GreenHopper

Labels:
None
Edit Labels

18 Comments

Hide/Show Comments

  1. May 30, 2011

    Anonymous

    How can I identify the so-called committed version in the database? I've browsed to most of the tables trying to find information about the version hierarchy, but no luck so far...

    1. May 30, 2011

      Nicholas Muldoon [Atlassian]

      Hello,

      It sounds like you may be interested in GHS-1853. Feel free to comment and watch that issue for updates.

      Thank you.
      Nicholas Muldoon

      1. Sep 24, 2011

        Anonymous

        Hi I think he's just asking where the information is stored in the DB, not trying to hack the source code.

  2. Jul 06, 2011

    Anonymous

    Hello,

    is it possible to set a master version for a few different projekt versions?

    Thank you for your help.

  3. Sep 14, 2011

    David Hyman

    How do I configure Greenhopper to display versions in a descending order. I would like my most current sprint to appear at the top.

     

    I have tried many times to configure this and I cannot figure out how to do it for the life of me... please help!

     

    Thanks in advance! 

  4. Sep 22, 2011

    Anonymous

    I've got the same problem as David described - I need to reorder versions (they appear in reverse order on versions panel though are displayed correctly in Add versions window).

    Would be thankful for any advice.

    1. Nov 24, 2011

      Anonymous

      +1

      1. Jan 31, 2012

        Anonymous

        +1

        1. Feb 03, 2012

          Anonymous

          GH shows versions according to their's order in Project Versions administration page.

          So simply reorder them on the Versions page and update GH Planning Board to see result. 

  5. Oct 11, 2011

    Anonymous

    Is there any way to do the following:

    I have 2 dev teams, we'll call them A and B. Each one has their own sprint, which we set up with a parent Fix Version of 'Sprint 3' and Fix Versions of 'Sprint 3A' and 'Sprint 3B' respectively. Usually, this works fine because at the end of Sprint 3, all code is released, so all 3 Fix Versions can be marked as released. But what if team B happens to be working on a couple of issues in a branch that will be done as part of our sprint cycle, but will not actually be released until a few other issues are completed in the next sprint (Sprint 4). AFAIK, when Sprint 3 is released, I have to use the release feature to mark Sprint 3, Sprint 3A and Sprint 3B released. Thus the 2 issues that were branched and therefore not released as part of Sprint 3 are now incorrectly marked as released. The other option is to not mark Sprint 3B as released, but then that wouldn't be correct for all the issues that did get released as part of that sprint.

    Am I using GreenHopper wrongly by tieing sprint cycles to Fix Versions? Is there a way to do the above?

    1. Oct 13, 2011

      Anonymous

      I believe that what you are looking for is written up in issue GHS-945. I was quite disappointed when it dawned on me that this limitation was in Jira/Greenhopper (sad).

      1. Nov 24, 2011

        Dan Burzynski

        Thanks for that link! I'll be watching for the GH 6.0 release like a hawk!

  6. Dec 07, 2011

    Anonymous

    I am unable to edit the parent field for any of the versions at right - the pencil icon does not show up... Ideas?

    1. Dec 08, 2011

      Rosie Jameson [Atlassian Technical Writer]

      Please note that you will need to have the JIRA 'Project Administrator' permission in the relevant project. I have now added this info to the page.

  7. Dec 28, 2011

    Anonymous

    Using Jira OnDemand. 

    How do I setup the default issue screen such that when I enter a version in the fix version field, it's parent is also populated in that field? Currently if I enter Sprint1, I want the Milestone (it's parent) also populated so that when I look at the planning view I can see all issues in the Milestone (Sprint 1, 2 3). But this doesn't happen. 

    Oddly, this is the behavior when I create new sub task from the submenu of any story in agile view but I want consistent behavior no matter how I create the issue.

    1. Jan 18, 2012

      Anonymous

      If I well understood, the only way to see in the Milestone version (parent) view all the issues included in Sprint versions (childs) is adding every issue to both versions (child and parent) when creating the issue?

      I thought that GreenHopper was able to consolidate all the issues from child versions just defining the parent relationship.

  8. Jan 20, 2012

    Anonymous

    I have found that if you use the "+Create Issue" from the main menu bar, the association to the parent version is not made. If you use the "+ New Card" link from your Task Board, Planning Board, etc..., it will include the parent version when creating the issue.

  9. Feb 03, 2012

    Oleg Semykin

    I've noticed that if I change parent for some Version on Planning Board, GH updates fix version to new parent for ALL issues planned for the child version.

    Even for Resolved and Closed ones.

    This is very strange, since JIRA restricts edit for Resolved issues, so I expected that GH also will conform that policy.

    It would be a great feature for Release planning in the middle of the sprint.

    The desired scenario is as follows:

    1. Create Version for next planned release. Let say: VER_1.0
    2. Create several sprint versions as children for VER_1.0
    3. Plan issues for the sprints
    4. Work, resolve and close issues in the sprints: versions SPRINT_1, SPRINT_2
    5. While SPRINT_3 is ongoing we decided to release the version VER_1.0 and continue development under VER_2.0
    6. Create VER_2.0
    7. Change parent for SPRINT_3 to VER_2.0
      1. All unresolved issues get new Fix Version: VER_2.0; SPRINT_3;
      2. All resolved issues stay unchanged with: VER_1.0; SPRINT_3
    8. Finally we get correct release history with appropriate issues included in the VER_1.0 release notes.

    Step. 7.b doesn't work now.

    May be GH has alternative ways to deal with "Release in the Middle" situation but it seems he doesn't.

    Please consider is it possible to implement.

    Thanks in advance,
    Oleg.