Personal issue timer for Jira®

When you start work on some issue, all you need is click on “Start timer” button and forgot about it. But when you want some coffee or have some important business call(or call from your mom) just don’t forgot to press “Stop timer” and do your stuff. At end of a day you will have a perfect timing for all issues you do. When you don’t need some timer anymore, log your work or press “Drop timer” button and timer will be deleted.

As describer up, you can start timer for any issue you can see. Even if you don’t have any edit permission for this issue. This helps you to track time when you help your teammates. And you can log this time later, when you will have edit permission.

When you need to switch fast from current task to new one, open new task page and start timer for this task. Previous active timer will be stopped automatically. When you finish urgent task just switch to previous task, click Start timer button and move on from paused state. At once you can have only one active timer.

When you log time spent for task in any way, your personal timer for this task will be deleted automatically. That helps you to see time for last unlogged interval only and free you from any time calculating ever.

If you don’t need timer for issue, press “Drop timer” button manually and confirm, that you want remove current timer value. IMPORTANT. “Drop timer” will not call any time logging actions in Jira®. It just drop current timer data from system.

From any Jira® page you will have access to list of all your personal existing timers. Timers dropdown menu in Jira® navigation bar will helps you for that. This menu contains all your personal existing timers with values. Currently active timer will have a green background. Else you can see there link with total number of existing counters, that forwards you to your Jira® homepage, and “Clear all my timers” link, that will immediately drop all your timers data. IMPORTANT. “Clear all my timers” link simply call “Drop timer” action for ALL user timers, so any logging actions will be NOT called.