Project

General

Profile

Actions

Feature #18126

open

Allow setting up version hierarchy

Added by Dzianis Frydliand over 9 years ago. Updated almost 8 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Roadmap
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:

Description

There's useful feature in JIRA which we would like to see in Redmine.

JIRA allows you to create parent-child relationships between versions. For example, you may wish to group your sprints as milestone versions (e.g. "Version 1 m1", "Version 1 m2", etc) under the version for the major release (e.g. "Version 1").

In JIRA, you can set up the major version as the "parent" version for the milestone versions. This allows you to view and track all of the issues assigned to the milestone releases under the umbrella of the major release.

All issues under the child version are considered to be a subset of the parent version. These version hierarchies are useful for managing Releases/Sprints/Teams. For example, if you set 'Version 2' to be the master of 'Version 2 milestone 1', then you will be able to view all the issues assigned to 'Version 2 milestone 1' when you view 'Version 2' on the Planning Board.


Related issues

Related to Redmine - Feature #13387: Improving Redmine's version model (not just milestones)New

Actions
Related to Redmine - Feature #8991: Nested versions for projects with sub-projectsNew2011-08-05

Actions
Actions #1

Updated by Dzianis Frydliand over 9 years ago

Plannig Board = Roadmap in Redmine

Actions #2

Updated by Toni Smillie over 9 years ago

Yes please. I'd like this feature too.
I want to be able to see burndowns at the iteration level and at the release level. Having a heirarchy would be great

Actions #3

Updated by Toshi MARUYAMA over 9 years ago

  • Category set to Roadmap
Actions #4

Updated by Sebastian Paluch over 9 years ago

+1!

Actions #5

Updated by Ge Ko over 8 years ago

any news on version hierarchy? Would very much like if this will become true soon.

Actions #6

Updated by Toshi MARUYAMA over 8 years ago

  • Related to Feature #13387: Improving Redmine's version model (not just milestones) added
Actions #7

Updated by Dave Lowndes over 8 years ago

+1

We need the ability to have several releases (sprints) within a release. Each sprint needs a name and date, i.e. a child version attached to a version!

1.0.0 Minimum viable product
- sprint 1 alpha (5/2/2016)
- sprint 2 beta (19/2/2016)
- sprint 3 rc (4/3/2016)
1.1.0 - New features
- sprint 1 beta (18/3/2016)
- sprint 2 rc (1/4/2016)

We then need the ability to group by child version to see all issues, by sprint, planned for a release as well as all issues in the whole release (e.g. for release notes).

Actions #8

Updated by Inese Ez over 8 years ago

+1!

Actions #9

Updated by Dipan Mehta about 8 years ago

Add related - #8991

Actions #10

Updated by Dipan Mehta almost 8 years ago

Though more elaborate - this issue is essentially a duplicate of #453

Also add this and #453 to overall issue - #13387 in the larger study.

Actions #11

Updated by Toshi MARUYAMA almost 8 years ago

  • Related to Feature #8991: Nested versions for projects with sub-projects added
Actions

Also available in: Atom PDF