Transition Technology: Ticket #345: TRAC time 'add hours' not working

status changed

chris — Wed, 21 Sep 2011 17:09:26 GMT

status changed from new to accepted

I have confirmed this, will look into it tomorrow

estimatedhours changed

chris — Thu, 22 Sep 2011 09:25:31 GMT

estimatedhours changed from 0 to 0.2

I have upgraded to the latest version of this plugin, see wiki:TimingAndEstimationPlugin for install notes

 cd ~/timingandestimationplugin/trac0.11
 svn up
 python setup.py bdist_egg
 sudo cp dist/timingandestimationplugin-0.9.8-py2.6.egg /web/tech.transitionnetwork.org/trac/plugins/

hours, totalhours changed

chris — Thu, 22 Sep 2011 09:46:54 GMT

hours changed from 0.0 to 0.1
totalhours changed from 0.0 to 0.1

Testing adding time...

hours, totalhours changed

chris — Thu, 22 Sep 2011 10:09:40 GMT

hours changed from 0.0 to 0.4
totalhours changed from 0.1 to 0.5

I have opened a ticket about this here https://trac-hacks.org/ticket/9196

hours, totalhours changed

chris — Thu, 22 Sep 2011 10:12:35 GMT

hours changed from 0.0 to 0.03
totalhours changed from 0.5 to 0.53

Testing

hours, totalhours changed

chris — Thu, 22 Sep 2011 10:14:25 GMT

hours changed from 0.0 to 0.1
totalhours changed from 0.53 to 0.63

Hmm it all seems to be working now :-)

chris — Thu, 22 Sep 2011 10:17:37 GMT

What is somewhat confusing is that the position of the timer has moved.

hours, status, totalhours changed; resolution set

chris — Thu, 22 Sep 2011 10:51:02 GMT

hours changed from 0.0 to 0.1
status changed from accepted to closed
resolution set to fixed
totalhours changed from 0.63 to 0.73

So this is working OK now, closing ticket.

hours, status, totalhours changed; cc set; resolution deleted

chris — Thu, 22 Sep 2011 11:40:53 GMT

cc ed added
hours changed from 0.0 to 0.3
status changed from closed to reopened
resolution fixed deleted
totalhours changed from 0.73 to 1.03

OK, so there is a problem here after all.

It looks like the totalhours field didn't exist before and the total time was kept in the hours field and now when time is added to an existing ticket it does wipe out previous hours, so these need adding back, but adding them back will change when they were done and also in the case of several people booking hours to a ticket the hours will need adding back by each person.

There shouldn't be a problem for new tickets or for times after the first new comment to a ticket.

I'm looking at things at a database level and at the tickets for this plugin: https://trac-hacks.org/query?status=closed&component=TimingAndEstimationPlugin&order=priority

hours, totalhours changed

chris — Thu, 22 Sep 2011 12:26:58 GMT

hours changed from 0.0 to 0.41
totalhours changed from 1.03 to 1.44

I don't think my comments above are right, something odd was happening but it seems OK now - I couldn't find any references to this problem and it seems to be working OK now...

status changed; resolution set

chris — Thu, 22 Sep 2011 12:28:19 GMT

status changed from reopened to closed
resolution set to worksforme

chris — Thu, 22 Sep 2011 14:23:01 GMT

Perhaps the problems only occurred between the upgrade to squeeze and the upgrade of the timing plugin?