Documentation for GreenHopper 6.2.x. Documentation for earlier versions of GreenHopper is [available too].

Planning a Version

Created by Rosie Jameson [Atlassian], last updated on May 09, 2013 1 minute read

This page only applies to Scrum boards.

A version is a set of features and fixes released together as a single update to your product. Assigning issues to versions helps you plan the order in which new features (stories) for your product will be released to your customers.

In GreenHopper you can view your issues according to which version they belong to, and drag-and-drop issues into the relevant version(s). This helps you plan your upcoming versions, which may span multiple sprints.

Go to Plan mode and click VERSIONS at the left of the screen (or select Tools > Show Version Panel).

画面左にバージョンのリストが表示されます。バージョン名をクリックすると、そのバージョンに属するすべての課題を、すべてのスプリントにわたって見ることができます。

この章の内容:

関連ページ

Screenshot: viewing versions in Plan mode

The blue horizontal bar indicates progress towards completing the work estimated for the version. Note that this bar is only shown if the version's issues have been estimated.

A GreenHopper version is the same as a JIRA version. You can use the JQL fixVersion field to search for a version's issues — see the JIRA JQL documentation for details.

11 Comments

Garrick S. Bodine
Apr 04, 2013
We were very excited about this feature, but are having some issues in getting to work. It works great on our boards that are defined by a filter that includes only a single project. Unfortunately because of the way our teams and apps are structured, that's not a realistic scenario for us. In our case we usually use a board filter that includes the project and also certain specific labels so that we can draw certain related issues from other projects into a sprint, which works great. As soon as a board filter is created that includes labels, however, all versions disappear from the GH board . I'm hoping (since this is in Labs) that this is a bug related to the fact that it's still being developed and rather than a design choice. Is this a known issue, a design decision, or should I file it as a bug? Thanks.
EDIT: Looks like the last GH version fixed this. Thanks.
Drew Cox
Mar 28, 2013
Version planning is exactly what we are looking for, but the amount of meta-data available for a version is pretty limited, name, description and release date. We would like to have some planning dates, the ability to record dependencies on a release from other teams etc. Any ideas?
1. Rosie Jameson [Atlassian]
  Apr 01, 2013
  We are working on more features around version planning. Please expect to see enhancements in the near future. You may like to search http://jira.atlassian.com/ghs for relevant feature requests, or log new ones.
alan lippa
Mar 29, 2013
this is exactly what we have been looking for.

WE are an On-Demand Customer, how do I enable this under system?
1. Rosie Jameson [Atlassian]
  Apr 01, 2013
  This will be available in the next OnDemand release. Thank you for your patience.
Andreas Worm
Apr 17, 2013
The progress bar does not seem to work as it does with the epics.
We have got GH 6.1.6 and a fixVersion with issues from a single project , some resolved, some open. The progress bar stays gray. I guess that's in development?
1. Rosie Jameson [Atlassian]
  Apr 19, 2013
  The blue progress bar relies on estimates having been made for issues in the version.
  1. Andreas Worm
    Apr 19, 2013
    Nevermind. Updating to 6.2 just fixed it.
Patrick Coleman
Jun 06, 2013
Using GreenHopper 6.2.2 and I'm wondering if it is a future planned enhancement to mark a version as done like you can for epics. We have lots of historical versions which just clutter up the Planning board.
1. Rosie Jameson [Atlassian]
  Jun 07, 2013
  I haven't yet seen a request for this – you may like to raise one at http://jira.atlassian.com/browse/GHS
  1. Patrick Coleman
    Jun 07, 2013
    Created GHS-9116 - Getting issue details... STATUS