Edgewall Software

Opened 17 years ago

Last modified 15 months ago

#2344 new enhancement

sub milestone

Reported by: anonymous Owned by:
Priority: low Milestone: next-major-releases
Component: roadmap Version: 0.9
Severity: major Keywords: milestone tracobject hierarchy submilestone
Cc: planders@…, cjunge@…, olemis+trac@… Branch:
Release Notes:
API Changes:
Internal Changes:


I need the feature to create children milestones.

For example, I planned V1_release as a milestone. OK. Now suppose I plan alpha, alpha2, beta, beta2, rc1, rc2 release, then I'd like to associate these releases as parts of "V1_release".

I'd like to assign these small milestones as children of greater milestone.

Or another example, suppose gnome development process, they have some of phases for each release. Feature freeze, String freeze, Hard UI freeze, etc.

If trac supports sub-milestone, then it is possible to manage these kind of release/development process.

Attachments (0)

Change History (21)

comment:1 by Christian Boos, 16 years ago

Keywords: tracobject added
Owner: changed from Christopher Lenz to Christian Boos

See also #886 and the SubTickets proposal.

comment:2 by Christian Boos, 15 years ago

Milestone: 2.0

Another long term goal…

comment:3 by Christian Boos, 15 years ago

Keywords: hierarchy added
Milestone: 2.01.0

#4004 was closed as a duplicate.

comment:4 by planders@…, 14 years ago

Another use case for this would be to categorize high level features or subsystems within an overall release. In project planning this is sometimes called a Work Breakdown Structure. Even a very simple capability of associating milestones in a parent-child relationship would satisfy most my personal project management requirements. I don't necessarily need or want SubTickets (as I understand that) because I need this hierarchy reflected in the Milestones screen and not in each ticket.

Keywords in tickets partially fulfill my requirements in that they can associate sets of tickets for custom reports but what I'm missing is the ability to tie this into the Milestones feature. If anyone has any preliminary implementation ideas I could take a crack at it.

Thanks for your time, and thanks for developing great software like Trac!

comment:5 by planders@…, 14 years ago

Cc: planders@… added

comment:6 by cjunge@…, 14 years ago

Cc: cjunge@… added

comment:7 by fcorreia@…, 14 years ago

Another use case would be to support iterative development.

In my particular projects i'd like to create a milestone for each version i plan to release in the future. However, each version development will be composed by several iterations. It would be perfect being able to create a sub-milestone for each iteration, so that i'd be able to track the progress of iterations on the roadmap page and, at the same time, track the overall progress of the version to be released.

Could this possibly be included in trac 0.12? (i guess inclusion in 0.11.x is out of the question right? would be great though…)

comment:8 by fcorreia@…, 14 years ago

Keywords: submilestone added

comment:9 by fcorreia@…, 14 years ago

I'm seeing some things in common between the idea i've described above and the concept of "sprint" that the agilo plugin tries to achieve: http://groups.google.com/group/agilo/browse_frm/thread/d20e413b93a895a0

I think submilestones would be much more flexible though, as they could be used for sprints/iterations or other objective.

comment:10 by jpierson@…, 14 years ago

I've been waiting for this type of functionality in Bugzilla as well. If Trac implements milestone and component hierarchies I'll likely consider converting over our company's Bugzilla installation to a Trac site instead.

comment:11 by anonymous, 13 years ago

Another Usedcase form ProjectView:
We use Milestones for Releases. To Each Release, there are several Projects planned. This can't be implemented.

comment:12 by Ryan Ollos <ryano@…>, 13 years ago

Cc: ryano@… added

comment:13 by anonymous, 13 years ago

An easy(ish) way to do this may be the same way as blocked by/blocking within the ticket system(?) Would provide basic hierachy without breaking anything that already exists.

…would be good if this could become a "short-term" goal rather than long-term! Any chance of getting it into a 0.12 release?

comment:14 by Christian Boos, 12 years ago

Milestone: 1.02.0

#8936 also exposed the need for distinction about milestone types (see in particular ticket:8936#comment:4).

In some organisations, "Milestone" can already have an accepted meaning, more precise than the broad "version/release/ticket group" catch-all concept we have (see also #4236, though the discussion quickly derailed, unfortunately).

So maybe we could think about having different Milestone "types", a bit similar to the way we have ticket types, but done better (different realms and sub-classing, see GenericTrac).

comment:15 by Christian Boos, 12 years ago

Milestone: 2.0unscheduled

Milestone 2.0 deleted

comment:16 by Christian Boos, 12 years ago

Milestone: triagingnext-major-0.1X
Priority: normallow
Severity: normalmajor

comment:17 by Ryan J Ollos, 9 years ago

Cc: ryano@… removed

comment:18 by olemis+trac@…, 9 years ago

Cc: olemis+trac@… added

comment:19 by Ryan J Ollos, 7 years ago

Owner: Christian Boos removed

comment:20 by David Banner <dbwonderchild@…>, 7 years ago

What is the progress on this?

comment:21 by figaro, 15 months ago

The requested functionality can be emulated using one of the following plugins:

  1. ExtendedVersionPlugin
  2. ListMilestonesMacro
  3. SimpleMultiProjectPlugin

Of these, the latter is currently the most up to date, but may require more configuration work to get set up for your purposes.

Modify Ticket

Change Properties
Set your email in Preferences
as new The ticket will remain with no owner.
The ticket will be disowned.
as The resolution will be set. Next status will be 'closed'.
The owner will be changed from (none) to anonymous. Next status will be 'assigned'.

Add Comment

E-mail address and name can be saved in the Preferences .
Note: See TracTickets for help on using tickets.