Tickets :: Comment on [#6550] Support accumulating timers and ask for time entry when creating timer

* Your Email Address
* Spam protection	Enter the letters below: .__ .__ .___._.. . [__)[__)[__ \| \|\/\| [__)[__)\| _\|_\| \|
Comment	>> 1. When you create a timer, you must fill in the time entry's > >> "static" information: client, job type, cost object as well as a > >> "name" for the timer. > > > > I would change "must" to "can". > > > >> 2. When you click the timer, you see (but cannot edit) the previously > >> entered information. You also see (but cannot edit) the date and > >> accumulated hours. You are prompted to enter a description and > >> optionally notes. You have two options: Save and continue timing, or > >> Save and stop timing. > > > > I don't exactly follow the interface flow here. And what do you mean > with "previously entered information"? Already running timers? > > What happens with running timers anyway? Are they paused while > another timer is running? Is the last active timer resumed > automatically once a later timer has been stopped? > > > >> Thoughts? > > > > I'm not sure, do you consider this as a replacement for the > stopwatch, or next to it? Anyway, it sounds like a nice enhancement.
Attachment
Watch this ticket