GreenHopper 5.1 Release Notes


15 July 2010

The Atlassian team are proud to announce the release of GreenHopper 5.1. This release provides full compatibility with JIRA 4.1, bringing you the new-look JIRA interface plus a host of other enhancements.

To assist you when allocating work, we have added new levels of organisation:

  • On the Planning Board, you can now further filter assignees and components by version; and drag-and-drop a marker to set a temporary capacity.
  • On the Task Board, you can now further filter version by assignee.

To save you time when editing/moving/deleting multiple issues at once, JIRA's 'Bulk Change' functionality is now available when you select multiple issues on the Planning Board.

Also, when creating a new issue of type 'Epic', the issue's own issue key is automatically put into the 'Epic' field. This is a small improvement sure to induce a smile.

Upgrading to GreenHopper 5.1 is free for all customers with an active GreenHopper license.

Highlights of this release:

Thank you for your feedback:

25 new features and improvements implemented
29 votes fulfilled

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 5.1

You can download GreenHopper from the Atlassian website. If upgrading from a previous version, please read the GreenHopper 5.1 Upgrade Guide.

Highlights of GreenHopper 5.1

 

Planning Board Categorisation of 'Assignee' and 'Component' Modes by Version

To assist you when allocating work, we have added a new level of organisation to the Planning Board. You can now further filter an assignee's (or component's) issues by selecting a particular version, e.g.:

For more details, please see the documentation on Using Classic Planning Board Modes.

 

Task Board Categorisation of 'Version' Mode by Assignee

To assist you in managing assignees' workload, we have added a new level of organisation to the Task Board. You can now further filter a version by selecting a particular assignee, e.g.:

For more details, please see the documentation on Using the Classic Task Board.

 

'Bulk Change' available on the Planning Board

To save you time when editing/moving/deleting multiple issues at once, JIRA's 'Bulk Change' functionality is now available when you select multiple issues on the Planning Board.

Simply select 'Bulk Change' from the 'Tools' menu:

See the documentation for more details.

 

Marker Enhancements on the Planning Board

From GreenHopper 5.1, markers will now be available on the 'Component' and 'Assignee' modes of the Planning Board, instead of only the 'Version' mode.

Sometimes, for example when allocating work, you may want to temporarily change the value of a Marker for just the current version, component or assignee — without changing the Marker permanently for all versions, components or assignees. You can now do this easily by dragging a Marker bar up or down to set a temporary value for that Marker.

And yes, you can also move a marker to another location on another page of the Planning Board.

See the documentation for further details.

 

Improved Epic Creation

To make it quicker and easier for you to create Epics, the issue key of a newly-created Epic is now put into the 'Epic' field automatically. For more details, please see the documentation on Working with Epics in JIRA Agile Classic.

 

Other Enhancements

GreenHopper 5.1 introduces a range of additional enhancements:

  • When generating Release Notes, the configuration process has been streamlined.

  • When dragging multiple cards (e.g. when ranking issues), highlighting is enhanced and the number of cards is shown in red in the top right-hand corner:

 

For the Curious

GreenHopper 5.1 introduces a 'Labs' option, giving you a sneak preview of new features coming in future releases. See JIRA Agile Labs.

 

Plus over 30 Fixes and Improvements

The issues for GreenHopper 5.1 are shown below. To view the list in JIRA, please see here.

type key summary priority status votes

Data cannot be retrieved due to an unexpected error.

View these issues in Jira
Last modified on Apr 29, 2013

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.