
Note that this page only applies if you are using the
Classic Boards (which are no longer being actively developed;
read more).
If you are using the new boards, please see
Planning a Version.
GreenHopper allows you to create a new JIRA version without leaving the GreenHopper interface.
Adding a Version
To add one or more new Versions,
- Log into JIRA.
You will need to have the JIRA 'Project Administrator' permission in the relevant project. Select Agile > Classic in the top navigation bar. Then select Classic Planning Board from the drop-down below the project name.
- Click the Add link at the top of the right-hand panel. The 'Add Version' window will display (see screenshot below). Complete the fields as follows:
- Version name — Enter a short name for your new version. For details, see the JIRA documentation on Managing Versions.
- Parent (optional) — Enter the parent version for your new version. For details, see the GreenHopper documentation on Setting Up a Version Hierarchy.
- Start date (optional) — Enter the planned start date for your new version. Required for generating time based statistics.
- End date (optional) — Enter the planned end date for your new version.
- Release date (optional) — Enter the planned date of release for your new version. For details, see the JIRA documentation on Managing Versions.
- Description (optional) — Enter a longer description for your new version. For details, see the JIRA documentation on Managing Versions.
- 次のいずれかを実行します。
- Click the Create button to save your new version and keep the 'Add Version' window open so that you can add another version; or
- Click the Create and Close button to save your new version and close the 'Add Version' window
You can edit the Start date and End date later if you need to, via the 'Statistics' column of the Planning Board.
Screenshot: Adding a new version in GreenHopper
gh-50-add-version.png
16 Comments
David Fischer (Appfire)
Dec 09, 2010The difference between the "End date" and the "Release date" is unclear. In a Scrum context, should we fill in both with the same value? Should we use only one?
matthew thompson
Feb 24, 2011end date could be sprint end
release date is when actual release would occur (release could have multiple sprints)
Anonymous
Jul 18, 2011why those dates are readonly once set? is that by design or a permission issue?
Nicholas Muldoon [Atlassian]
Jul 19, 2011Hello,
The dates are not read only. You can update the Start, End and Release Date via the version box on the right hand side of the Planning Board.
Thank you.
Nicholas Muldoon
Steven Ginn
Jul 25, 2011Unfortunately, after a version is marked "Released" the dates become read only (which makes sense).
However the Cumulative Flow diagram doesn't work, unless a start date is specified.
Is there a way to go back in and fill in a start date? (or do i need to Unrelease, set start date, and release again?)
Nicholas Muldoon [Atlassian]
Jul 26, 2011Hi Steven,
You will need to unrelease, set the start date and then release once again.
Thanks,
Nicholas Muldoon
Michael Jones
Oct 12, 2011For some reason on our installation: JIRA (v4.4#649-r158309) & GreenHopper (v5.7.1) the dates are greyed out in all 3 boxes and can not be entered manually.
Anonymous
Nov 22, 2011What timezone is the start and end dates being used with? And how does the timezone relate to issue statistics? Any relation to new User timezones feature in Jira?
Balaji Sundara
Feb 09, 2012If a version is already exists then how do we get to see it in Planning Board?
Nicholas Muldoon [Atlassian]
Feb 09, 2012Make sure that it is Unreleased. GreenHopper will not show any Release Fix Versions on the Planning Board.
Thanks,
Nicholas
Balaji Sundara
Feb 10, 2012The version I am talking about is unreleased. We are currently still assigning items to it and I do not see that version displayed in Planning Board ?
Anonymous
May 10, 2012Hi Nicholas,
A common question I've seen on a number of these comment areas is 'How can I control the display order of child versions in the Statistics column on the Planning Board?" Typically when i create a new Version it generated at the bottom of the existing non-released Versions however if a new Version is created and related to a Parent Version then the new version displays as the first line below the parent. Typically when planning a release we start with the first version and build out - the default way Jira appears to work requires us to start with the last version and work backwards.
Is there a way to configure our Statistics column so that new children versions appear at the bottom of the children list ?
Your help is appreciated.
Nicholas Muldoon [Atlassian]
May 11, 2012Hello,
No way to configure this unfortunately. The workaround is to go into Project Administration -> Versions and drag and drop the versions to change the order there.
This will not be an issue on the Rapid Board. For more information see The Future of GreenHopper.
Thanks,
Nicholas
Anonymous
Jul 19, 2012Hi Nicholas,
How can I assign issues to a particular version? Cheers
Anonymous
Sept 14, 2012Hi Nicolas,
Dates (start and end) are greyed in our application. Could you tell us how to change this dates? What is the problem? Lack of permisions or sth else?
Thanks
Christopher Warin
Jan 16, 2013Is there a way to create a sprint from items that are not in the backlog?
For example we have 10 items in the fixed version 1.0 and want to create 2 sprints out of this.