Add start date to a milestone

[daan@…]

It would be nice to have a start date for a milestone. With that, it's possible:

• To filter on started/not started milestones on the Roadmap page
• Create reports to show only tickets in currently active milestones
• Sort on started date in the 'Milestone' dropdown on the ticket create and update pages.

With a start date built-in, plugins could use that (for example the Scrum Burndown plugin) to draw their graphs. The Scrum Burndown plugin now has to arrange a column, while it could be useful for more plugins.

[fcorreia@…]

(just listening)

[Christian Boos]

Custom field for milestones …

[Christian Boos]

Milestone experimental deleted

[stefan.simroth@…]

I would find that also incredibly useful, so I'm listening, too.

I'd like to create a Gantt chart from the Roadmap / Milestones for a better overview.

[Thijs Triemstra]

Makes a lot of sense.

[liltor@…]

adding my 2 cents for this one

[Steve Nixon <steve.nixon@…>]

A milestone start date also allows calculation of how accurate (predicatble) we are performing. The difference from the Start-date to the Due-date and Completed-date can then be compared. Were we early, on time or late?

This would improve project planning in general as well as making this kind of information visible to stakeholders ion the project.

[Christian Boos]

Idea: workflow for milestones, e.g.

start = new -> active finish = active -> closed finish.set_resolution = completed pause = new, active -> onhold cancel = active, onhold -> closed cancel.set_resolution = cancelled restart = closed, onhold -> active

[Christian Boos]

And of course, proper history, so each change is tracked and has a modification time associated to it.

[framay <franz.mayer@…>]

Replying to comment:10 of cboos:

Idea: workflow for milestones, e.g.

OT: cool, I didn't know that you could do workflow-graphs in Trac. Shouldn't it be listed in WikiProcessors#AvailableProcessors?! Maybe all available processors should be listed dynamically by a macro / processor?!

Replying to comment:11 of cboos:

And of course, proper history, so each change is tracked and has a modification time associated to it.

Change history for milestones would be really useful. But wasn't there a discussion about making milestone "just a special ticket"? I haven't found it at once (searched for "milestone as ticket").

[Peter Suter]

Replying to framay <franz.mayer@…>:

OT: cool, I didn't know that you could do workflow-graphs in Trac. Shouldn't it be listed in WikiProcessors#AvailableProcessors?! Maybe all available processors should be listed dynamically by a macro / processor?!

See #10270. It's a new macro, so it's listed (by the MacroList macro) at 0.13/WikiMacros. Not sure, maybe the ProcessorList macro from #10201 could in the future also list it on the WikiProcessors page.

But wasn't there a discussion about making milestone "just a special ticket"? I haven't found it at once (searched for "milestone as ticket").

#3003 maybe?

[Ryan J Ollos <ryano@…>]

comment:10 sounds great to me, but also outside the scope of the request in this ticket. I'd find it incredibly valuable to have a start date for milestone, and have even considered creating a plugin to add this. Creating the plugin would be challenging (and fun) for me, but I imagine that adding a start date is trivial for the Trac developers, and would just like to emphasize how useful this feature would be, and how appreciative I'd be if this were added :) To put it simply, as a starting point I'd just like to know the time span for a milestone, and be able to quickly determine the number of tickets closed in a milestone. Plugins could use this data to derive more complex metrics.

[Ryan J Ollos <ryano@…>]

Replying to Ryan J Ollos <ryano@…>:

To put it simply, as a starting point I'd just like to know the time span for a milestone, and be able to quickly determine the number of tickets closed in a milestone.

Poor wording. More precisely, I'd like to be able to quickly determine the burndown rate to an end-point spanning multiple milestones - (Number of tickets closed in a milestone) / (time span for the milestone).

[Ryan J Ollos <ryano@…>]

#10674 was created after some observation about how the WorkFlow macro behaves in comment:10.