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

* Your Email Address
* Spam protection	Enter the letters below: __ . .__.. ,.___ / `\| \| \| \./ [__ \__.\|___\|__\ \| [___
Comment	> 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.
Attachment
Watch this ticket