https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292014-10-17T11:46:33ZRedmineRedmine - Feature #18126: Allow setting up version hierarchyhttps://www.redmine.org/issues/18126?journal_id=591962014-10-17T11:46:33ZDzianis Frydliand
<ul></ul><p>Plannig Board = Roadmap in Redmine</p> Redmine - Feature #18126: Allow setting up version hierarchyhttps://www.redmine.org/issues/18126?journal_id=597382014-11-12T13:01:04ZToni Smillie
<ul></ul><p>Yes please. I'd like this feature too.<br />I want to be able to see burndowns at the iteration level and at the release level. Having a heirarchy would be great</p> Redmine - Feature #18126: Allow setting up version hierarchyhttps://www.redmine.org/issues/18126?journal_id=598112014-11-16T04:12:12ZToshi MARUYAMA
<ul><li><strong>Category</strong> set to <i>Roadmap</i></li></ul> Redmine - Feature #18126: Allow setting up version hierarchyhttps://www.redmine.org/issues/18126?journal_id=599972014-11-25T06:58:52ZSebastian Paluch
<ul></ul><p>+1!</p> Redmine - Feature #18126: Allow setting up version hierarchyhttps://www.redmine.org/issues/18126?journal_id=667422015-10-20T15:27:50ZGe Ko
<ul></ul><p>any news on version hierarchy? Would very much like if this will become true soon.</p> Redmine - Feature #18126: Allow setting up version hierarchyhttps://www.redmine.org/issues/18126?journal_id=673272015-11-16T03:49:41ZToshi MARUYAMA
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-1 priority-4 priority-default" href="/issues/13387">Feature #13387</a>: Improving Redmine's version model (not just milestones)</i> added</li></ul> Redmine - Feature #18126: Allow setting up version hierarchyhttps://www.redmine.org/issues/18126?journal_id=695722016-03-08T01:47:54ZDave Lowndes
<ul></ul><p>+1</p>
<p>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!</p>
<p>1.0.0 Minimum viable product<br />- sprint 1 alpha (5/2/2016)<br />- sprint 2 beta (19/2/2016)<br />- sprint 3 rc (4/3/2016)<br />1.1.0 - New features<br />- sprint 1 beta (18/3/2016)<br />- sprint 2 rc (1/4/2016)</p>
<p>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).</p> Redmine - Feature #18126: Allow setting up version hierarchyhttps://www.redmine.org/issues/18126?journal_id=697492016-03-18T09:23:03ZInese Ez
<ul></ul><p>+1!</p> Redmine - Feature #18126: Allow setting up version hierarchyhttps://www.redmine.org/issues/18126?journal_id=713252016-06-06T15:01:40ZDipan Mehta
<ul></ul><p>Add related - <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Nested versions for projects with sub-projects (New)" href="https://www.redmine.org/issues/8991">#8991</a></p> Redmine - Feature #18126: Allow setting up version hierarchyhttps://www.redmine.org/issues/18126?journal_id=718022016-06-27T04:47:56ZDipan Mehta
<ul></ul><p>Though more elaborate - this issue is essentially a duplicate of <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: a version includes many versions (Closed)" href="https://www.redmine.org/issues/453">#453</a></p>
<p>Also add this and <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: a version includes many versions (Closed)" href="https://www.redmine.org/issues/453">#453</a> to overall issue - <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Improving Redmine's version model (not just milestones) (New)" href="https://www.redmine.org/issues/13387">#13387</a> in the larger study.</p> Redmine - Feature #18126: Allow setting up version hierarchyhttps://www.redmine.org/issues/18126?journal_id=719742016-07-04T04:38:06ZToshi MARUYAMA
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-1 priority-4 priority-default" href="/issues/8991">Feature #8991</a>: Nested versions for projects with sub-projects</i> added</li></ul>