Closed (won't fix)
Project:
Quick Timetracking for Storm (Project Management)
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
10 May 2010 at 22:58 UTC
Updated:
28 Nov 2011 at 19:32 UTC
Comments
Comment #1
juliangb commentedI cannot reproduce this bug.
Comment #2
neubreed commentedYou might need to log some time and then see if it sets it to false.
The area of the code is between line 315 and 332 of storm_quicktt.module
Seems to set the variable false and then true again for some reason .. No many comments in the code that explains why.
Comment #3
juliangb commentedMoving to Storm Quick Timetracking project.
Comment #4
jurgenhaasThis is by design. The code is restoring the value in your settings every time it had to change it temporarily. So, there shouldn't be any issue I suspect.
The reason we have to do this is that while tracking time we periodically save the time used for a task and as we allow to pause a task while tracking time we have to make sure that stormtimetracking_auto_duration is set to FALSE because otherwise a possible pause wouldn't be recognized.
A posssible bug causing a problem may have been that in earlier versions we used AJAX async mode which sometimes send 2 requests at once and that left some values in a wrong state. But we have removed that a long time ago, in the dev release as of 1st June 2010.
Comment #5
kfritscheWorks as designed, so setting this to won't fix.
If there is still a problem, please report back.