Index![]()
[Downloads (PDF, HTML & XML formats)]
[Other versions]
Documentation for GreenHopper 6.2.x. Documentation for earlier versions of GreenHopper is [available too].
24 May 2012
The Atlassian team announces the release of GreenHopper 5.9.8, delivering Tracking Statistics and other enhancements to the Rapid Board.
This release also includes a number of fixes.
Upgrading to GreenHopper 5.9.8 is free for all customers with an active GreenHopper license.
You can upgrade GreenHopper via the JIRA Plugin Manager. Before upgrading, please read the GreenHopper 5.9.8 Upgrade Notes.
Please note: Plan mode is available by activating the "Scrum" option in GreenHopper Labs.
Previously, once you'd started a sprint, effectively the burndown never changed, so if the remaining estimate was 10, and you added another issue to the sprint, nothing would change; and if you removed an issue from a sprint, it would appear to have burnt down.
But now, once the sprint starts, if you add another issue to the sprint, then the graph will change to reflect scope change.
The Sprint Report (previously known as the Sprint Retrospective Report) now shows burndown, and also displays a table showing you which issues were completed successfully during the sprint and which were not.
GreenHopper will now suggest a name for your new sprint based on your previous sprint, e.g. if your previous sprint was called "Bob 1", GreenHopper will offer "Bob 2" as the default name for your new sprint.
In GreenHopper 5.9.7 we introduced the ability to choose your own Estimate Statistic; now you can do the same for your Tracking Statistic too.
This means that, for example, you can now choose to use Story Points for estimation, but time-tracking for burndown.
If you do not have an Estimation Statistic applied to an issue, you will receive a warning when starting the sprint (unless your Estimate Statistic is set to Issue Count, which is calculated automatically).
By popular request, you can now remove an issue from an in-progress sprint in Work mode. Simply click the cog icon in the issue's Detail View:
Once all the sub-tasks have been completed, it's time to resolve the parent issue. In GreenHopper 5.9.5 we introduced a prompt, when you move the last sub-task to the 'Done' column in Work mode, to remind you to move the parent too.
But what if you resolved the sub-tasks in native JIRA instead? In GreenHopper 5.9.8, we now display a button the next time you visit Work mode:
When you end a sprint, the Burndown Chart will now be displayed automatically.
GreenHopper 5.9.8 includes the following updates and bug fixes: