Open any Jira Cloud work item and look for a start button. There isn’t one. Jira lets you log work after the fact, but it has no timer. No play button, no running clock, no “stop timer.”
That surprises a lot of people, and it’s the reason “Jira timer” is one of the most searched phrases around time tracking in Jira.
This article covers what Jira’s native time tracking does, where it stops, what makes a timer work for a real team (and where timers go wrong), and how to pick one of the Jira time tracking plugins without regretting it in six months.
Does Jira have a built-in timer?
No. Jira’s native time tracking is a manual system. Here’s what you get:
- A time tracking field on the work item: original estimate, remaining estimate, and time spent.
- A Log work dialog where you enter time spent, the date you started, a work description, and choose how the remaining estimate changes.
- Worklogs, which are the individual time entries stored on each work item.
- Basic reports, such as a time tracking report for a sprint or version, and gadgets for your Jira dashboard.
That’s enough to log time and see totals per work item. It isn’t enough if you want to start a clock when you begin a task, switch between several tasks in a day, or see time logged by person and week.
➡️ We cover that last part in our guide to Jira time tracking reports.
Timer or manual entry? Both have a place
Teams rarely pick just one. Here’s how the two methods compare.
| Timer | Manual entry |
|---|
Best for | Focused work you can time as you do it | Catching up at the end of the day, short tasks |
Accuracy | High, if the timer is stopped on time | Depends on memory |
Weak spot | Forgotten timers, switching tasks | Round numbers, Friday guesses |
Effort | Low, when it works | A few minutes every day |
The biggest difference is accuracy. When you log time from memory, you feel like you’re taking liberties, because you’re a poor judge of how long things took.
Numbers drift toward eight hours here, four hours there. Live timers fix this because the data comes from the work itself. If you care about accurate time tracking and about better estimates later, the timer is the stronger habit.
Still, many teams end up with a mix. Some people like to track live, others prefer to go back and add the time after the fact. A tool that supports both avoids a fight about it.
Where timers go wrong
A timer sounds simple, and then the real week happens. These are the problems that show up again and again.
- The endless timer. Someone clicks start before lunch on Monday, and the entry is still running on Wednesday. Now the logged hours are nonsense, and someone has to fix them by hand. A running timer on a work item that is no longer in an active status is a classic example. Check for these in your weekly review.
- Small tasks. Timing a five-minute question is more effort than the question. Some teams simply don’t track anything under half a day, and log half a day or a full day when the work is done. That’s a fine rule as long as everyone follows the same one.
- Switching between work items. If you jump between projects all day, starting and stopping a timer each time gets tiring. Look for a timer that lets you stop one entry and start the next quickly, and that lets you restart the same work item without re-typing the description.
- Forgetting to start. You were already 45 minutes into a task when you remembered. Can you move the start time back? Not every timer lets you, so test it before you commit.
- Time with no work item. Meetings, admin and internal work don’t always have a ticket. In Jira, worklogs live on work items, so you’ll need a few standing items (meetings, admin, support) to log against. Decide these on day one.
- Overlapping tasks. People don’t finish one thing before starting the next. If your team works on several tasks in parallel, make sure your tool handles overlapping time entries and doesn’t assume one task at a time.
What to look for in a Jira timer app
There are plenty of Jira time tracking plugins on the Atlassian Marketplace, and they differ more than the listings suggest. This checklist helps you compare time tracking tools without testing all of them.
- Does it sync with Jira worklogs, both ways? A two-way sync means time logged in the app appears in Jira, and time logged in Jira appears in the app. If it’s one-way, you’ll end up with two versions of the truth.
- How do people log time? Timer, manual entry, calendar, inside the Jira work item. Choose what your team will actually use.
- Can you fix a mistake? Edit the start time, split an entry, restart a stopped one.
- Where does it run? Some apps add a browser extension, a desktop app or mobile support. Others work only inside Jira Cloud. Decide whether your team needs that, or whether the Jira integration is enough.
- What do the reports look like? You’ll want a time tracking report by person, project and date range, with export data options (CSV or Excel).
- Does it handle billable hours? If you do client billing, you need to separate billable from non-billable time.
- Is there a free plan, and how is pricing structured? Check how many users the free plan covers, and what happens when you grow. “Free time tracking” often means a limit on users.
- How is the app vetted? The Atlassian Marketplace runs a bug bounty program for apps. Check whether an app takes part, and read the security details on the listing.
Jira time tracking in Planyway
Planyway for Jira is a cross-project planning app that combines roadmaps, resource management, time tracking, reports, and other project management tools you might need down the road. Its time tracking is built to work with Jira’s own worklogs rather than replace them.
Here are the key features of Planyway's time tracking:
- Timer inside the work item. Start the timer on a work item, add an optional work description, and stop it when you finish. When you stop the timer, the worklog is created in Jira for you.
- Manual entry in several places. Log time in the work item, in the Time tracking list, on a calendar by dragging a work item onto a day, or in a personal timesheet by clicking a day and typing the hours.
- Two-way sync with Jira. Time logged in Planyway shows up in Jira’s time tracking field, and time logged in Jira shows up in Planyway.
- Reports in one place. Planned vs tracked with the deviation per task, Timesheets (+approvals), Tracked Time, Costs, plus billable and non-billable hours.
- Planning in the same app. The workload view and team capacity sit next to the logged time.
All time entries are linked to a Jira work item, the same as in Jira itself.
Btw, Planyway has a 30-day free trial and it’s free for teams of up to 10 people, so you can test it on your own projects first.
How to set up time tracking in Jira (step by step)
Whatever you choose, these steps decide whether people use it.
- Turn on the time tracking field for your Jira projects, so the original estimate and remaining estimate appear on work items.
- Agree on the unit. Hours or half days, logged live or daily. Write it in one sentence.
- Create standing work items for meetings, admin, and support.
- Set permissions. In Jira, people with the “Work on issues” permission can log time. Editing other people’s worklogs needs “Edit all worklogs”, so keep that for a few people.
- Pick one place to log time. Two tools means neither is accurate.
- Review weekly. Look for running timers, empty days, and entries that look too round.
What actual time spent is good for
Once the logs are accurate, you can use them for more than a total.
- Better estimates. Compare the original estimate with the actual time spent. If tasks of one type keep overrunning by 30%, change how you estimate them. Most teams get far better estimates after a few months of honest data.
- Client billing. With billable hours separated from other work, the monthly invoice stops being a spreadsheet exercise.
- Resource planning and team capacity. Actual hours show how long work really takes, which feeds resource allocation and capacity planning. See our guides on capacity planning in Jira and resource planning.
- Project progress. Time logged against the plan shows where a project is drifting while there’s time to act.
The bottom line
A Jira timer can save you from guessing how long a task took, but only if your team actually uses it. Forgotten timers, constant task switching, and hours logged at the end of the week can undermine even the best tool.
Start with a simple setup your team can stick to, whether that means live timers, manual entries, or both. Then use the data to do more than fill in timesheets: compare estimates with actuals, spot tasks that consistently take longer than expected, and plan future work based on what it really takes.
That’s when time tracking becomes useful — not just for knowing where the hours went, but for making better decisions about what comes next.
