Adding a manual timetracker / stopwatch to tickets/issues

Question

Hi for our project we would like an simple way to start/stop a stopwatch or something similar to track time manually on a issue. It is especially important this can be controlled  manually.

I've looked at several marketplace apps, and most are just way too complicated and don't quite meet our needs, we just want a button to start and stop a timer on an issue/ticket.

There is the time tracking feature native to Jira with the option to manually control it, but we use that to track time worked on an issue. Not possible to add a second one?

Simply setting a start/end datetime at the end doesn't meet our needs, there could be intervals in between etc.

Any suggestions to approach this problem?

Edit: reading my own question it seems like I rule out all external apps, this is not the case. To clarify further I've looked specifically at Everhour Time Tracking Integration For Jira.

Fatma Uzundemir from The Starware · Answer

Hi @J B

It’s unfortunate that Jira’s built-in time tracking feature doesn’t fully meet your needs.

If you’re open to third-party apps, I can recommend one that’s simple to configure and easy to use: WorklogPro Timesheets for Jira.

🌱 With  WorklogPro Timesheets for Jira, you can start timers for specific issues, and you can even add multiple timers to the same issue. When you stop or close a timer, the time tracking panel for that issue opens automatically.

🌱 From there, you can easily log your work—time and issue details are automatically filled in; all you need to do is click Save.

🍀 You can take a look at the app via the link if you’d like: WorklogPro Timesheets for Jira. 🍀

Disclaimer:I work for the vendor who developed this application.

Anton from JetHeads_io · Answer

Hey!

JetTime is pretty straightforward for this — it has a timer right under each issue that you can start/stop manually, and it logs the time as a worklog when you're done. No extra complexity, just clean manual control.

Also includes:

* Improved Log Work UI if you need to adjust entries
* Custom metrics and cost tracking if your workflow grows
* Runs fully on Atlassian infrastructure

Worth checking out if you want something simple that doesn't overcomplicate things.

👉 JetTime on the Atlassian Marketplace
— Anton, JetTime founder

Birkan Yildiz _OBSS_ · Answer

Hello @J B

That's an excellent question. I’ll suggest a different approach to address this problem of yours.

A simple and powerful way to handle this is to use your Jira workflow as your "stopwatch," which avoids adding a new, complex UI.

Here is how:

When you start work on the issue, transition it to an "active" status, like says In Progress.

When you stop or pause, transition it to a "paused" status, for example Block.

You can do this as many times as you need, which creates the ‘'intervals’' you mentioned.

Now, Jira has no built-in report to show you the total time an issue spent in In Progress by assignee, especially after it's been 'Block' multiple times.

This reporting gap is exactly what Timepiece - Time in Status for Jira (which is built by my team at OBSS) is designed to solve. It uses your issue's history to analyze the data you're already creating.

With the workflow above, you can run the "Assignee Duration per Status" report.

This report shows you a perfect grid of every assignee and every status, with the total cumulative time spent in each. It automatically sums up all those "intervals" for you.

I hope this helps! Please let me know if you have any further question, and visit Timepiece’s marketplace page.