Multiple Milestone Dates

[anonymous]

It would be nice to be able to assign multiple dates to a milestone. For example I might want a CodeComplete date, TestingComplete date and a Launch date.

[Noah Kantrowitz]

Why can't those be separate milestones?

[ThurnerRupert]

take 0.11 of trac:

you have a date when you would switch it on on teo, a date when you do rc1, and release. having a milestone on each of this might confuse the users, as finally you have just one version, 0.11, released.

maybe the better annotation for this would be "milestone workflow", and a target date for the steps/status in the workflow?

[Christian Boos]

Replying to ThurnerRupert:

take 0.11 of trac:

you have a date when you would switch it on on teo, a date when you do rc1, and release. having a milestone on each of this might confuse the users, as finally you have just one version, 0.11, released.

So you would have 3 dates to guesstimate instead of just one. This would confuse the developers even more.

All kidding put aside, I think that this would rather be done using a workflow for milestones, and the timeline would present the status changes of the milestone (e.g. new → started → testing → released → retired) as major events when they happen, as opposed to when they're supposedly due.

(simple milestone description edits would be minor events - same distinction as for tickets, see also #3776, #5730).

[ThurnerRupert]

hehe. point taken - it was a bad example. but in some companies you have such a scheme with quite fixed dates and release numbers, but the contents is important, but not so much.

maybe a milestone is a ticket (#3003), and tickets belong to this automatically solves all this. hmm. or submilestones (#2344).

[Noah Kantrowitz]

This can be done with multiple milestones and a naming scheme (0.11-RC1, 0.11-Alpha, etc etc).

[sid]

Other option is to put as many dates as you want in the description of the milestone. That won't affect the sorting, but should be visible in the same way.

[Christian Boos]

So this looks more a use case for Milestone workflow here (with optionally dates associated to each state).

• code_complete
• testing_complete
• launch

[Christian Boos]

Milestone 2.0 deleted

[Christian Boos]

Related to #1942 and having custom fields for milestone (a.k.a. #3911, GenericTrac etc.).

About comment:7 and associating dates with workflow events, I think it would indeed be interesting to be able to record the timestamp for some transitions. Typical example would be to record the actual "close" time for a ticket, for making it possible to use that information in custom queries.