[Trac] Re: Trac`ing the time spent on tickets.

[Justus Pendleton]

Felix Collins wrote:
> All this would allow us to do some cool stuff like a report showing % 
> completion of a milestone based on time estimates and time spent.
> 
> It is important to keep an initial estimate because this allows 
> retrospective assessment of the initial estimate accuracy.

It almost sounds like you want to version control the estimates, as it 
seems likely that some estimates will change multiple times.  I don't 
know whether keeping those intermediate estimates would be useful for 
project tracking purposes, however.

> Would anybody care to hazard a guess as to how hard this would be to 
> implement?

I haven't looked at the ticket stuff but based on what I've seen of the 
rest of trac's internals I'd say it probably wouldn't take more than a 
day or two for someone proficient in python.  The inside of trac is 
fairly straight forward and there really isn't a ton of code to 
overwhelm and confuse you.  I would suggest you add file a ticket for 
this feature if you decide not to implement it on your own, as I agree 
it sounds like it could be nifty.

> Would this feature be likely to make it into the trunk?

Christopher Lenz recently mentioned he's the only person with commit 
access who is actively working on trac.  So it'd probably be up to him :-)