On Apr 9, 9:01 am, "Chris Nelson" <chr...@sixnetio.com> wrote: > >> To effectively display project progress, tickets must have estimated > >> and actual times as in the TimingAndEstimation plugin. > > > Is this sched vs execution (plan vs real progress ;) time? > > My bias is for the way we use it here: actual is how much time you've put in. > Estimate is how long it's expected to take. When we accept a ticket, we put > in an initial estimate. If we find out that the task is much more or less > complex than originally believed, we revise the estimate. Time remaining is > always estimate-actual. However, since this seems to be a matter of > contention, I think I'd take Yogi Barra's advice (When you get to a fork in > the road, take it.) and add a configuration option to specify whether > remaining time is in the DB or must be computed.
Personally, I'd like to see 3 values - the original estimate, the actual work time spent, and the remaining estimate. During development, I am most interested in the current estimated time remaining. After completion it can be useful to compare the time it actually took with the initial estimate. - jevans --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
