On Feb 11, 10:41 am, Christian Boos <cb...@neuf.fr> wrote: > Chris Nelson wrote: > > We use Trac 0.11 and the Timing and Estimation plug-in. We're trying to > > get better at estimating by analyzing how initial estimates on our last > > project matched up with final actual hours. But we'd also like to keep > > track of when and by how much milestones were rescheduled (presumably due > > to estimates being wrong, but sometimes due to other factors). Milestones > > don't seem to have any history. Is there a plug-in or hack for that? Am I > > looking at this problem the wrong way? > > Hello Chris, > > There's already a few tickets requesting to add an history to > milestones, see #1673 and #3776. > > -- Christian
We had this need also. I actually found it easiest to create a new milestone, and forward the remaining open tickets to the "special" milestone. Helps us see which tasks we under-estimated, or where we took on more than we could chew. Assuming the "incomplete" things were executed later in the dev cycle for the milestone. It sometimes helps to point out potential feature creep, the things that don't get worked on are actually nice to have. I know not what everyone wants, but it does serve the purpose for us. Additionally, we keep a wiki page with info like this. an Entry such as "milestone X moved from day 1 to day 2 would be created. This is something that you just don't do that often, in theory. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
