Ticket #3081 (closed enhancement: fixed)

Opened 5 years ago

Last modified 3 years ago

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

Reported by: izekia Assigned to: bobbysmith007
Priority: lowest Component: TimingAndEstimationPlugin
Severity: minor Keywords: patch
Cc: fcorreia@gmail.com, macke@yar.nu Trac Release: 0.11

Description

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.

Attachments

reports.patch (4.7 kB) - added by izekia on 05/27/08 12:20:42.
reports patch

Change History

05/27/08 12:20:42 changed by izekia

  • attachment reports.patch added.

reports patch

05/27/08 15:19:58 changed by bobbysmith007

  • priority changed from normal to lowest.
  • severity changed from normal to minor.
  • summary changed from A little inconsistency in reports to Extra remaining hours after the ticket is closed inconsistency.

Thanks for the patch!

05/27/08 15:20:12 changed by bobbysmith007

  • keywords set to patch.
  • summary changed from Extra remaining hours after the ticket is closed inconsistency to Extra remaining hours after the ticket is closed inconsistency [Patch].

01/03/09 13:28:06 changed by FilipeCorreia

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

01/03/09 13:28:37 changed by anonymous

  • cc set to fcorreia@gmail.com.

02/18/09 10:58:36 changed by macke@yar.nu

  • cc changed from fcorreia@gmail.com to fcorreia@gmail.com, macke@yar.nu.

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?

02/18/09 11:24:00 changed by macke@yar.nu

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

05/07/09 16:59:37 changed by bobbysmith007

Linked this patch from the main wiki page

02/24/10 16:02:04 changed by bobbysmith007

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.

08/24/10 15:26:58 changed by bobbysmith007

  • status changed from new to closed.
  • resolution set to fixed.

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.

Add/Change #3081 (Extra remaining hours after the ticket is closed inconsistency [Patch])




Change Properties
Action