I just tried to create a version hierarchy from the Planning board (Planning Board > Version > Add), but I wonder why the order of the child versions is inversed. I did the following:
But on the Planning board (right column), the versions are displayed in the following order:
I would have expected:
And in the Project Administration page, the versions are listed in the following order (I realize, that this page always shows all the versions in reverse, but that's not the problem!)
I would have expected:
Why does JIRA/GreenHopper order it that way (especially given that GreenHopper understands child versions as sprints summing up to the parent version, see http://confluence.atlassian.com/display/GH/Setting+Up+a+Version+Hierarchy) ?
The project administration page in JIRA treats the versions as a flat list and uses explicit ordering (there is 'sequence' attribute of the version object). You can control it using the 4 blue arrows in the table. It might be a good enhancement request to add a 'Order all versions based on release date' button.
GreenHopper uses ordering by release date - See Colin's answer for details. (Note that release date is used for ordering, not start/end dates, which are used for things like charts and estimation metrics)
Once I assign release dates, GreenHopper actually reorders the child versions on the planning board. JIRA's Project Administration page does not however.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
(I'm using JIRA (v4.3.4#620-r152668) & GreenHopper (v5.6.8))
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.