Blog ·
Jira for time tracking: log work, read it back, and close the week
Jira for time tracking works out of the box: every Jira Cloud space can record an estimate on a work item, a log of the time people spent on it, and the time remaining. What Jira does not do is make anyone log their hours. The setup takes ten minutes, reading the numbers back takes a saved filter, and the hard part is the habit: the Friday timesheet, the month-end review, the hours that only get entered when someone chases them. This guide covers all three, in that order.
A note on words: Jira Cloud now calls projects spaces and issues work items in much of its interface. This article uses both, since most teams still say "issue".
What Jira's built-in time tracking gives you #
As of October 2026, Atlassian's administration guide says time tracking "is enabled by default in Jira", and that you "won't lose any existing data if you disable or re-enable it". The built-in feature covers three values on each work item:
| Value | What it holds | Who usually sets it |
|---|---|---|
| Original estimate | How long the work should take, set before it starts | The person planning the work |
| Time spent | The total of every work log entry | Whoever does the work |
| Time remaining | What is left, adjusted as time is logged | Jira, or the person logging |
Each entry in the work log has a person, a date, a duration and an optional description. That is enough for most teams to answer "where did the week go" and "was the estimate right".
What it does not give you out of the box: approval of timesheets, billing rates, a grid where someone fills in a whole week at once, or reports across many spaces in one view. Those are what the Marketplace time tracking apps sell, and the section on apps below covers when one is worth it.
Step 1: set time tracking up #
Three settings decide whether the numbers mean anything. A Jira admin finds them under Settings, then Work items, then Time Tracking in the sidebar, and Edit global settings.
- Working hours per day and working days per week. These turn "1d" into hours. If your team works a 7.5 hour day and the setting says 8, every estimate in days is off by half an hour per day. Atlassian notes that decimal values are accepted.
- Default unit. The unit used when someone types a bare number. Atlassian's guide, as of October 2026, says that if you type "2" instead of "2h", "the default time unit set by your Jira admin will apply". Pick hours unless your team thinks in days.
- Time display format. Pretty, Days or Hours. Hours is the easiest to add up in a report.
Then two things per space:
- Permissions. Logging time needs the Work on work items permission in the space's permission scheme. Editing or deleting entries needs the separate Edit own worklogs, Edit all worklogs, Delete own worklogs and Delete all worklogs permissions. Give most people the "own" versions and keep the "all" versions for whoever reviews timesheets.
- The field. Time tracking is always on in Jira Cloud, but the field has to be visible. In a company-managed space it is shown or hidden in the field configuration and has to be on the create and edit screens if you want an estimate entered at creation. In a team-managed space you add the Time tracking field to each work type that needs it.
Step 2: estimate, then log as you go #
Estimating and logging are separate habits, and teams that skip the first can still get value from the second.
To estimate, open the work item and fill in Original estimate. Jira accepts weeks, days, hours and minutes, so 2d 4h 30m is valid. Scrum teams often estimate stories in story points instead; time estimates still work on subtasks and tasks.
To log time, open the work item, choose More actions and Log work, or select the time tracking field. Fill in the time spent, the date, and what you did. The command palette (Ctrl + K or Cmd + K) reaches the same action from the keyboard.
A few habits make the log useful later:
- Log against the work item, not a catch-all ticket. A single "Admin time" ticket hides where the hours went. A small number of recurring tickets (see Step 4) is fine, because each one names a real routine.
- Write the description. "Reviewed PR, fixed two comments" turns the log into a record someone can read at month end.
- Log on the day. An entry dated last Tuesday and typed in on Friday is a guess.
One limit is worth knowing before you build reports on parents. As of October 2026, Atlassian's guide says that if a work item has more than 100 child work items, "you can't include them in time tracking", and it recommends keeping to 100 children per parent.
Step 3: read the hours back with JQL #
The work log is only useful if someone reads it. JQL has fields for exactly this, so a saved filter can answer the questions a timesheet answers.
| Question | JQL |
|---|---|
| What did I log this week? | worklogAuthor = currentUser() AND worklogDate >= startOfWeek() |
| What did the team log last week? | project = OPS AND worklogDate >= startOfWeek(-1) AND worklogDate < startOfWeek() |
| Which done items have no time logged? | project = OPS AND statusCategory = Done AND resolved >= startOfMonth() AND timespent IS EMPTY |
Two things to know. JQL cannot compare two fields, which Atlassian states plainly in its JQL field reference as of October 2026, so "spent more than estimated" is a column you sort by, not a query. Add the Original estimate, Time spent and Remaining estimate columns to the list view and sort. And the worklog fields find the work items that have matching entries; the number of hours per person is in each item's work log, so for a total by person you export the list or use a report.
Once a filter answers the question, subscribe to it so the answer arrives by email. Our Jira weekly report guide walks through filter subscriptions step by step, and the same subscription works for a "done but no time logged" check every Monday.
For a team view, put two of these filters on a dashboard. Our Jira dashboard examples show which gadgets read a filter.
Step 4: put the time tracking routine on a schedule #
The setup above makes time tracking possible. It does not make it happen. In most teams the gaps are the same every month:
- The weekly timesheet. Hours from Monday are forgotten by Friday unless something asks for them.
- The month-end review. Someone has to check that every done item has time on it before the numbers go to finance or to a client.
- Recurring work with nowhere to log. The standup, the weekly ops review, the monthly patch window. If there is no ticket for it, the time goes to a catch-all or nowhere.
Each of these is a work item that should appear on a date, every week or every month. There are three ways to get it there.
| Clone by hand | Jira Automation scheduled rule | Recurring Work Items for Jira | |
|---|---|---|---|
| Setup | None | One rule per routine | One rule per routine |
| Title per run | Typed each time | Smart values | Tokens checked on save |
| Uses Automation quota | No | Yes | No |
| Scope | One person's memory | Rule scope you choose | One project |
| When it stops | Someone forgets | Rule can disable after repeated failures | Each run recorded with a reason |
Cloning by hand works until the person who does it is on leave. A Jira Automation rule with a Scheduled trigger and a Create work item action is the native option, and each run counts toward your plan's monthly automation usage; our Jira Automation pricing article explains how that is counted.
How it looks in Recurring Work Items for Jira #
Recurring Work Items for Jira is our app, and the time tracking routine is a natural set of rules for it.
- Turn the app on for the project and choose who may schedule.
- Create a weekly rule for Friday:
Timesheet check {{now.date}}, assigned to each team lead, with the "this week" filter linked in the description. - Create a monthly rule for the first working day:
Time review for last month, assigned to whoever signs off the hours, with the "done but no time logged" filter in the description. Holidays and weekends are skipped by the working week you set for the project. - For recurring meetings and chores, create one rule each, so the standup or the patch window gets its own ticket to log against every time it happens.
Because it runs on its own scheduler, it uses no Jira Automation quota, and every run, whether it created, skipped or failed, is written to the rule's history. It is scoped to one project, so the time review for one team never lands in another team's space. It is free for up to 10 users.
Do you need a time tracking app? #
The Marketplace has many time tracking apps, and Jira lets an admin swap the built-in feature for one under Time tracking provider in the same settings page. Atlassian's guide notes that with a third-party provider, "your data might be stored with the app developer", so read the app's data security statement first.
An app is worth it when you need:
- a weekly grid where people fill in all their hours at once;
- timesheet approval by a manager;
- billable and non-billable hours, rates, or invoices to clients;
- reports across many spaces and teams in one place.
The built-in feature is enough when:
- you want estimates against actuals for planning, and nothing more;
- a few people log time and one person reviews it;
- the reporting you need is "who logged what this week", which the filters in Step 3 answer.
Scheduling the routine is separate from either choice. A timesheet app still needs someone to open it on Friday, and a reminder ticket works with any provider.
When the manual way is enough #
Not every team needs the schedule in Step 4.
- One person logs time for their own planning. A calendar reminder on Friday is enough, and our Jira reminder guide covers the options inside Jira.
- Time is logged for estimates only. If nobody reviews the hours at month end, there is no review ticket to create.
- The team already has a weekly ritual. If the timesheet check happens in the daily standup on Fridays, a ticket adds nothing.
It is worth scheduling once hours go to finance or a client, once more than one team logs time, or once a month-end review has been skipped because nobody remembered it.
Summary #
| Need | Where it lives in Jira |
|---|---|
| Hours per day, default unit | Settings, Work items, Time Tracking |
| Who can log and edit time | The space's permission scheme |
| Estimate and log on an item | Original estimate and Log work |
| Hours by week or person | Saved filters on worklogDate and worklogAuthor |
| The weekly and monthly routine | A recurring ticket, by Automation or a scheduling app |
For planning with the estimates you collect, see Jira capacity planning, and for the weekly status write-up that often sits beside the timesheet, the Jira weekly report.
Frequently asked #
Is time tracking free in Jira? Yes. The built-in time tracking is part of Jira Cloud and, as of October 2026, Atlassian says it is enabled by default. Marketplace apps that replace it are priced separately.
Can Jira remind people to log their time? Not by itself. A filter subscription can email a list of work items with no time logged, and a recurring ticket, created by a Jira Automation rule or by an app such as Recurring Work Items for Jira, can put the timesheet check on the board every Friday.
Can I edit someone else's work log? Only with the Edit all worklogs permission in that space.
Want the Friday timesheet check to show up on its own? Install Recurring Work Items for Jira and write the rule once.