Documentation for GreenHopper 6.2.x. Documentation for other versions of JIRA Agile is available too.
GreenHopper is now called JIRA Agile. Learn more.
This release delivers the following enhancements:
This release also includes a number of fixes. For full details please see the GreenHopper 6.0.3 Release Notes and GreenHopper 6.0.4 Release Notes.
To make sure you are always seeing the latest data, GreenHopper now refreshes the board periodically if the browser window does not currently have focus. It sends a poll request to the server every 30 seconds with a checksum and if this has changed, the server sends back the new board data. If GreenHopper detects an out-of-date board while you have focus on the window, it will show a message asking you to refresh: We would love your feedback on this new feature (note that it has currently been implemented for Work mode only). Please comment on
GHS-5568
-
Getting issue details...
STATUS
.Auto refresh
By popular request, you can now choose which fields to show in the Issue Detail View. At this time you can choose any custom fields of type "Text" — more to follow very soon in future releases. See Configuring the Issue Detail View for further details. You now have an instant visual indicator of what type of board you are looking at, thanks to the following icons: Scrum board Kanban board We have added these icons to the Agile drop-down menu: The icons are also shown at the top left of each board: For boards that are configured to use Time Tracking there are two improvements to make the management of the Remaining Estimate on issues and sub-tasks easier. In Plan mode, the sprint footer will now display the sum of the Remaining Estimate of all of the issues and sub-tasks in the future sprint. Note that the the value will not be shown if: In Work mode, the value shown on the bottom right of the card is now the Remaining Estimate for the issue or sub-task: To help newcomers get started quickly, we've included sample data with GreenHopper. You can now have multiple active, parallel sprints. For example, if you have two teams working fom the same backlog, each team can now work on their own sprint. Please note the following caveats with this simple approach: This feature is currently in Labs – please enable "Parallel sprints" to activate it. Please note that this feature is still undergoing development and may change from its current implementation.Customise your Issue Detail View
What type of board is that?
Easier management of Remaining Estimate
Sample data included
Parallel sprints