Extra remaining hours after the ticket is closed inconsistency [Patch]

[izekia]

Sometimes there was a difference between estimated hours and total hours when ticket already closed. So remaining hours displays wrong number of hours. I've made this patch for myself, but may be it will be helpful for somebody.

[izekia]

reports patch

[Russ Tyndall]

Thanks for the patch!

[Filipe Correia]

I'm for the inclusion of this ticket on the next release! Are there any plans in this regard?

[Marcus Lindblom]

This is pretty important for us too.

It's interesting to see the diff between expected and actual after the ticket has been closed, but the remaining effort should count as zero for a closed ticket.

Great plugin btw. Is there anything I can do to get this patch accepted?

[Marcus Lindblom]

This is related to #4603, but I think the bug is in this plugin

[Russ Tyndall]

Linked this patch from the main wiki page

[Russ Tyndall]

I might consider applying this patch, but I would like to hear why people think this is a bug. I mostly use the estimate vs total hours (time remaining) to tell how good I am doing estimating. Thus even on closed tickets I would rather see how far off I was from my estimates, rather than voiding all estimation errors down to 0 when the ticket is closed.

I dont actually use the built in reports terribly much, as I have trac integrated into our billing system at work, and have other reports that run across all of our trac instances. So, if my use case is stupid, or non-obvious to everyone else in the world, I could change it.

[Russ Tyndall]

I'm going to close this ticket, but it is documented on the TimingAndEstimationPlugin page. If you feel this should be addressed further please reopen.