Index
[Downloads (PDF, HTML & XML formats)]
[Other versions]
Documentation for GreenHopper 6.2.x. Documentation for earlier versions of GreenHopper is [available too].
See also What's New and Atlassian OnDemand Application Versions.
Please note that releases of GreenHopper "behind-the-firewall" (that is, GreenHopper for installation on-premises at your site) may occur several days before GreenHopper OnDemand is updated to the latest release.
GreenHopper OnDemand releases:
This release delivers the following enhancements:
This release also includes a number of fixes. For full details please see the GreenHopper 6.1.2 Release Notes, GreenHopper 6.1.3 Release Notes and GreenHopper 6.1.3.2 Release Notes.
We are pleased to announce that you can now find issues in a given epic by simply using the epic's name in your JQL search, e.g.:
"epic link" = Jupiter
You can still use the epic's issue key (as previously) if you wish, e.g.:
"epic link" = ANERDS-317
Please note that your administrator will need to re-index JIRA before you can search by epic name.
The Epic Report shows a list of complete, incomplete and unestimated issues in an epic. It is particularly useful for planning work for an epic that may extend over multiple sprints.
Use the Epic Report to understand the progress towards completing an epic over time, and to track the amount of remaining work that's incomplete or unestimated.
From Plan mode, you can now easily jump to the Issue Navigator and view/action your selected issues (see screenshot above).
Need to edit, transition, delete or move a bunch of issues? From Plan mode, you can now perform a JIRA Bulk Change on your selected issues (see screenshot above).
In GreenHopper 6.0.3 we introduced the ability to add text-fields to your cards; in 6.0.5, we added numeric fields; and in 6.0.8, we added date/time fields.
In 6.1.2, you can now also add custom fields of the following types:
By (very) popular request, you can now exclude weekends from your cycle time (that is, the time taken to resolve an issue).
For most teams, including the weekend will artificially inflate your actual cycle time. So now, when viewing the Control Chart, you can simply choose to exclude your non-working days:
We are pleased to announce that you can now find issues in a given sprint by simply using the sprint's name in your JQL search, e.g.:
sprint = "February 1"
You can still use the sprint's numeric ID (as previously) if you wish, e.g.:
sprint = 123
If you have multiple sprints with similar (or identical) names, you can simply search by using the sprint name — or even just part of it. The possible matches will be shown in the autocomplete drop-down, with the sprint dates shown to help you distinguish between them. (The sprint ID will also be shown, in brackets).
When viewing an epic in JIRA, you can now see a list of stories (issues) that belong to the epic:
If you were previously using epics on the Classic boards, you will be pleased to hear that it's now very easy to migrate your epics to your new boards.
For details please see Migrating Epics.
You can now click the "+" icon, at the top right of the Issues in Epic section, to conveniently add more issues to an epic when viewing an epic in JIRA:
Note that you can also still use the Create issue in epic link in Plan mode (as previously):
This release delivers the following enhancements:
This release also includes a number of fixes. For full details please see the GreenHopper 6.1.1 Release Notes.
You can now filter out weekends, holidays, and other times during which your team might not be working on a given project. Non-working days will be indicated on the Burndown Chart:
Each person who views the Burndown Chart can decide whether to hide/show non-working days.
The board owner can configure non-working days for each board:
We intend that these settings will also be reflected in the Sprint Report and the Control Chart in an upcoming release in the near future.
In GreenHopper 6.0.3 we introduced the ability to add text-fields to your cards; in 6.0.5, we added numeric fields; and in 6.0.8, date/time custom fields.
In 6.1.1 you can now also custom fields of the following types.
For details, please see Configuring the Issue Detail View, and the JIRA custom field documentation.
The icons for jumping to different sections of an issue — Details; Description; Comments; Attachments; Sub-tasks — are now displayed vertically at the left of an issue:
The icons are always available, even when you scroll down.
^top
This release delivers the following enhancements:
This release also includes a number of fixes. For full details please see the GreenHopper 6.1 Release Notes.
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.
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 GreenHopper 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.
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:
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.
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.