GreenHopper 4.2 Release Notes
23 November 2009The Atlassian team are proud to announce the release GreenHopper 4.2.
GreenHopper 4.2 includes a number of tweaks to make it easier for you to work with issues. We've introduced a statistical marker that you can optionally display on your Planning Board. You can use this marker to help determine how many issues you can assign to a version without exceeding your team's capacity.
Drag and drop functionality for cards/rows on all boards has also been improved in this release. You can now "shift-select" issues, allowing you to easily select multiple issues that are grouped together (Firefox, Safari and Chrome browsers only).
Upgrading to GreenHopper 4.2 is free for all customers with an active GreenHopper license.
Highlights of this release:
Thank you for your feedback:
8 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!
Highlights of GreenHopper 4.2
Statistical markers are a tool for your Planning Board that you can use to split your backlog into two groups of cards/rows, according to a statistic (e.g. story points). For example, if you are assigning issues from your backlog to a version, you can sort your cards/rows on your Planning Board then add a statistical marker. The statistical marker will visually divide your cards/rows based on the maximum capacity of the statistic (e.g. maximum story points your team can complete in a version). You can then assign all cards above the marker to your version, knowing that the maximum capacity will not be exceeded.
- Read Using Statistical Markers to Group Issues for more information.
GreenHopper now allows you to select multiple cards/rows that are grouped together by clicking one card then holding down the SHIFT key on your keyboard and clicking another card. You can still select multiple cards/rows that are not adjacent to each other
- Read Scheduling and Assigning Issues in JIRA Agile Classic for more information.
Was this helpful?
Thanks for your feedback!