Feature #18126: Allow setting up version hierarchy - Redmine

Actions

Copy link

Feature #18126

open

Allow setting up version hierarchy

Added by Dzianis Frydliand about 10 years ago. Updated over 8 years ago.

Status:

New

Priority:

Normal

Assignee:

Category:

Roadmap

Target version:

Start date:

Due date:

% Done:

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

Actions

Copy link

Updated by Dzianis Frydliand about 10 years ago

Plannig Board = Roadmap in Redmine

Actions

Copy link

Updated by Toni Smillie about 10 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

Copy link

Updated by Toshi MARUYAMA about 10 years ago

Category set to Roadmap

Actions

Copy link

Updated by Sebastian Paluch almost 10 years ago

+1!

Actions

Copy link

Updated by Ge Ko about 9 years ago

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

Actions

Copy link

Updated by Toshi MARUYAMA about 9 years ago

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

Actions

Copy link

Updated by Dave Lowndes over 8 years ago

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

Copy link