GreenHopper 6.1 Release Notes

10 December 2012

The Atlassian team announces the release of GreenHopper 6.1, launching epics out of Labs.

Highlights of this release:

This release also includes a number of fixes.

Thank you for your feedback:

Over 100 fixes and improvements implemented since GreenHopper 6.0
Over 500 votes fulfilled since GreenHopper 6.0

Your votes and issues help us keep improving our products, and are greatly appreciated.

Please keep logging your votes and issues. They help us decide what needs doing!

Upgrading to GreenHopper 6.1 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 Upgrade Notes.

If you are using GreenHopper OnDemand, please watch the JIRA Agile OnDemand Release Summary for the latest updates.

Organise your Stories into Epics

Epics provide you with an additional hierarchy of story management, providing planning guidance for groups of issues within, or across, projects. This allows ScrumMasters and Product Managers to measure important groups of issues that are all related by a common theme.

In GreenHopper 6.1 we are delighted to launch epics out of Labs. Epics are now automatically enabled for every Scrum board, appearing in the left-hand panel:

Originally released (via Labs) in GreenHopper 6.0.6, we added colour customisation and inline editing in GreenHopper 6.0.7. This was followed in GreenHopper 6.0.8 by progress bars, an Epics panel that follows you down the page, and the ability to create an issue that is automatically added to your chosen sprint.


Mark an Epic as "Done"

You can now exclude completed epics from Plan mode to keep it uncluttured.

Simply select Mark as Done in the epic drop-down:

Technical notes for the curious:  Epics now have a custom field called Epic Status, of type Status of Epic (for details please see JIRA Agile - JIRA Configuration). Marking an epic as "Done" will set the epic's Epic Status field to "Done", but will not affect the epic's workflow or its Status field, and none of the epic's issues will be affected.


View an Epic's History

Change History is now stored on the epic (as well as on the included issues), and is visible when you view the issue in JIRA.

For example, if issue SSP-1 is added to epic SSP-24, then SSP-1 will look like this:

... and SSP-24 will look like this:


Add Issues from Active Sprints to an Epic

In Plan mode, you can now drag-and-drop issues to an epic from either the backlog, a planned sprint or an active sprint.

See Adding an Issue to an Epic.


Clear Quick Filters in a Single Click

Ever used Quick Filters in Plan mode, and forgotten they were on? (We have.)

So now there is a Filtered icon  at the top of the backlog — and in each sprint header — to indicate that one or more filters have been applied. Click it to clear all filters.


Updates and Fixes in this Release

GreenHopper 6.1 includes the following updates and bug fixes:

Showing 20 out of 30 issues Refresh


Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport