Edgewall Software
Modify

Opened 12 years ago

Last modified 4 years ago

#5755 new enhancement

Multiple Milestone Dates

Reported by: anonymous Owned by:
Priority: low Milestone: next-major-releases
Component: roadmap Version:
Severity: normal Keywords: milestone date workflow object
Cc: Branch:
Release Notes:
API Changes:

Description

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.

Attachments (0)

Change History (10)

comment:1 by Noah Kantrowitz, 12 years ago

Why can't those be separate milestones?

comment:2 by ThurnerRupert, 12 years ago

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?

in reply to:  2 comment:3 by Christian Boos, 12 years ago

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).

comment:4 by ThurnerRupert, 12 years ago

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).

comment:5 by Noah Kantrowitz, 12 years ago

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

comment:6 by sid, 12 years ago

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.

comment:7 by Christian Boos, 11 years ago

Keywords: workflow added; roadmap removed
Milestone: 2.0

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

  • code_complete
  • testing_complete
  • launch

comment:8 by Christian Boos, 9 years ago

Milestone: 2.0unscheduled

Milestone 2.0 deleted

comment:9 by Christian Boos, 9 years ago

Keywords: object added
Milestone: triagingnext-major-0.1X
Priority: normallow

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.

comment:10 by Ryan J Ollos, 4 years ago

Owner: Christopher Lenz removed

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The ticket will remain with no owner.
The ticket will be disowned. Next status will be 'new'.
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.