[Tickets #12543] Re: Only one timer at a time should be active.

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12543
------------------------------------------------------------------------------
  Ticket             | 12543
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Only one timer at a time should be active.
  Queue              | Hermes
  Version            | Git master
  Type               | Bug
  State              | Assigned
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2013-08-07 18:01) wrote:

I guess I don't see why we would be charging time to two different  
cost objects/clients/whatever at once. But then again, I guess I'm  
assuming the timers are only used for timing billable events.

I had a timer running for another reason, but failed to stop it when I  
started a new one. While I can figure out what time to substract from  
the first one to make it "right" again, it can lead to overcharging a  
cost object if the user doesn't notice it didn't stop the other timers.

I guess an option when creating the timer to make it "exclusive" would  
work here as well.