Modify

Opened 6 years ago

Closed 4 years ago

#3081 closed enhancement (fixed)

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

Reported by: izekia Owned by: bobbysmith007
Priority: lowest Component: TimingAndEstimationPlugin
Severity: minor Keywords: patch
Cc: fcorreia@…, macke@… 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 (1)

reports.patch (4.7 KB) - added by izekia 6 years ago.
reports patch

Download all attachments as: .zip

Change History (10)

Changed 6 years ago by izekia

reports patch

comment:1 Changed 6 years ago 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!

comment:2 Changed 6 years ago by bobbysmith007

  • Keywords patch added
  • Summary changed from Extra remaining hours after the ticket is closed inconsistency to Extra remaining hours after the ticket is closed inconsistency [Patch]

comment:3 Changed 6 years ago by FilipeCorreia

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

comment:4 Changed 6 years ago by anonymous

  • Cc fcorreia@… added

comment:5 Changed 6 years ago by macke@…

  • Cc macke@… added

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?

comment:6 Changed 6 years ago by macke@…

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

comment:7 Changed 5 years ago by bobbysmith007

Linked this patch from the main wiki page

comment:8 Changed 5 years ago 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.

comment:9 Changed 4 years ago by bobbysmith007

  • Resolution set to fixed
  • Status changed from new to closed

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 Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.