Index
[Downloads (PDF, HTML & XML formats)]
[Other versions]
Documentation for GreenHopper 6.2.x. Documentation for earlier versions of GreenHopper is [available too].
21 March 2013
The Atlassian team announces the release of GreenHopper 6.1.5, bringing you:
This release also includes a number of fixes.
Upgrading to GreenHopper 6.1.5 is free for all customers with an active GreenHopper license.
If you are using GreenHopper "behind-the-firewall" (that is, if GreenHopper is installed on-premises at your site), you can upgrade GreenHopper via the JIRA Plugin Manager. Before upgrading, please read the GreenHopper 6.1.5 Upgrade Notes.
If you are using GreenHopper OnDemand, please watch the GreenHopper OnDemand Release Summary for the latest updates.
The Version Report now shows you the predicted completion timeframes for a version, based on your team's current daily velocity.
The graph shows you three lines:
Note that 10% of the estimated work for the version will need to be complete before the predictions can be calculated.
Your administrator will need to activate Release Planning in GreenHopper Labs before you can view the Version Report.
You can now easily see which epics are relevant to a particular version. When you click a version in Plan mode, epics which do not contain issues belonging to that selected version will be greyed out — e.g. "Pluto" in this screenshot:
To display all issues regardless of which version they belong to, simply click the "filter" icon:
Note that your administrator will need to activate Release Planning in GreenHopper Labs before you can view versions in Plan mode.
GreenHopper 6.1.5 is compatible with JIRA 6.0 EAP 7 (m9). At this point in time it is expected that GreenHopper 6.1.5 will be compatible with JIRA 6.0 beta and also with the official JIRA 6.0 release.
GreenHopper 6.1.5 includes the following updates and bug fixes:
4 Comments
Anson Hoyt
Mar 21, 2013We'll enjoy this fresh slice of functionality. Noticed an incorrect/missing link for JIRA 6.0 EAP 7 (m9).
Rosie Jameson [Atlassian]
Mar 22, 2013Thank you – that link will be live on Monday. Sorry for any inconvenience in the meantime.
Kim Poulsen
Mar 22, 2013Very nice work Atlassian.
How is the estimate calculated? If it is calculated from the onset of the first issue closed in that version to present date the prediction can/will get too conservative in the cases where a version is "put to rest" for a while (i.e. no issues closed for a long period) or worked on by a small team/single person, then started up again with a full team.
The graph here will look like a hyperbolic or parabolic function towards the release date basically.
A better (linear) estimate in this case would be to allow the user to set the estimation start date for this version to a date closer to the present date.
Rosie Jameson [Atlassian]
Mar 25, 2013We are actually working on allowing a Version Start Date to be specified (great minds think alike
) — please see
GHS-8023
-
Getting issue details...
STATUS
.
However, please note that that calculation will still be continuous across the period from the Start Date to today (ie. periods of inactivity will not be taken into account).
Hope this helps to some extent.