To enable time tracking in Jira: Settings → Issues → Time Tracking → Activate, then configure working hours. If Log Work isn’t appearing on a specific project, check that the Time Tracking field is in that issue type’s field configuration and that your role has the Work On Issues permission. Most “time tracking not working” problems come down to one of these three settings.
This guide is for the admin side of time tracking — enabling it correctly, configuring it for your organisation’s working hours, and fixing the handful of reasons it silently stops working for some users or projects.
Already configured and logging time? See how to log it correctly: How to Log Time in Jira: A Complete Guide for Teams. Need to report on time already logged? See: Jira Time Tracking: Complete Guide to Reports, Logging & Setup.
Enabling time tracking globally does not guarantee it appears on every project’s issues. Each issue type has its own field configuration, and Time Tracking can be hidden from it independently.
This is the single most common reason teams report “time tracking isn’t working” after confirming it’s enabled globally — it’s enabled site-wide but missing from the specific issue type’s field configuration.
Work through these in order — they cover the overwhelming majority of cases.
| Check | Where to look | What to fix |
|---|---|---|
| Is time tracking enabled globally? | Settings → Issues → Time Tracking | Set provider to JIRA provided time tracking, click Activate |
| Is the field in this issue type’s config? | Project Settings → Issue Types → [issue type] | Move Time Tracking from hidden to active fields |
| Does the user have permission? | Project Settings → Permissions → Work On Issues | Grant the permission to the relevant role |
| Is the issue in a restricted status? | Workflow configuration | Some workflows disable editing (including Log Work) on Done or Closed issues |
| Is this Jira Service Management? | Request type field configuration | Time tracking must be added to the request type, not just the underlying issue type |
Three fields work together to drive Jira’s time tracking system:
These three fields are what populate Jira’s native Time Tracking Report — which compares Original Estimate against Time Spent at the fix version level. If any of these three fields are missing from your field configuration, the report will show incomplete or zero data even if people are logging work.
Jira Service Management uses the same time tracking system as Jira Software, but the setup path is slightly different because request types — not issue types directly — control field visibility.
This is a frequent point of confusion — admins enable time tracking globally, see it work on Jira Software projects, then find it missing entirely on their Service Management request types because the field configuration step was skipped there separately.
Getting time tracking correctly configured is the foundation — but configuration alone doesn’t guarantee useful reports. A few additional things matter before you can trust the data:
Once your instance is correctly configured and your team is logging consistently, Report Hub‘s Timesheet report gives you a grouped per-user summary — total hours by person, project, and sprint — directly inside Jira Cloud, without exporting to spreadsheets or writing JQL queries. It reads the same worklog data this guide helps you set up correctly, so getting the configuration right here is what makes Report Hub’s reports trustworthy from day one.
Once time tracking is configured and your team is logging work, the natural next step is reporting on it. Jira stores every worklog — date, time spent, author, comment — but provides limited native options for surfacing it as a usable report.
Native option: JQL in Issue Navigator
The fastest way to pull a worklog report without any add-on:
This returns all issues where that user logged work this month. Export to CSV and sum the Time Spent column to get a total. It is not a grouped summary — it is a flat issue list that requires manual aggregation.
For a proper grouped work log report — total hours per user, per project, per sprint — without exporting to spreadsheets, Report Hub‘s Timesheet report handles this directly inside Jira Cloud.
Full guide: Jira Time Tracking: Complete Guide to Reports, Logging & Setup
“Time in status” refers to how long an issue spent in each workflow stage — for example, 2 days In Progress, 1 day In Review, 4 hours in QA. This is different from time logged via Log Work. Time in status is calculated from the issue’s history, not from manual worklog entries.
Jira Cloud does not have a native time in status report. The closest native option is the Control Chart (Kanban boards only), which shows cycle time but not a breakdown by individual workflow status.
For a dedicated time in status report in Jira Cloud — showing exactly how long issues spend in each stage across your workflow — teams use Marketplace add-ons. See: Jira Time in Status Report: How to Track How Long Issues Spend in Each Stage.
Several Marketplace apps extend Jira’s native time tracking with timesheet views, timers, and billing features that the built-in system doesn’t provide.
| Tool | Type | Best for |
|---|---|---|
| Report Hub | Jira Forge app (native) | Timesheet reports by user, project, and sprint — inside Jira Cloud, no data leaving Atlassian |
| Tempo Timesheets | Jira Marketplace plugin | Approval workflows for logged time, billable hour tracking, client invoicing — best for time-and-materials billing |
| Clockify | External tool with Jira integration | Timer-based time tracking — users start/stop a timer rather than manually entering time. Syncs back to Jira worklogs. |
| Jira Timer / Timetracker plugins | Various Marketplace apps | In-browser timer functionality for users who prefer tracking time as they work rather than logging retrospectively |
Go to Settings → Issues → Time Tracking → select JIRA provided time tracking as the provider → click Activate. Then configure working hours per day and days per week to match your organisation. Individual projects may still need the Time Tracking field added to their field configuration separately.
The most common causes: time tracking disabled globally (Settings → Issues → Time Tracking), the Time Tracking field missing from the issue type’s field configuration (Project Settings → Issue Types), or the user lacking the Work On Issues permission (Project Settings → Permissions). Check these three in order.
Go to the project → Project Settings → Issue Types → select the issue type → confirm Time Tracking is in the active field list, not hidden fields. This must be repeated for each issue type that needs time tracking since field configuration is per issue type, not per project.
Three core fields: Original Estimate (predicted time before work begins), Time Spent (actual logged time), and Remaining Estimate (time left, auto-updated or set manually). These populate Jira’s native Time Tracking Report, which compares estimate accuracy at the fix version level.
Go to Settings → Issues → Time Tracking → adjust “Hours per day” and “Days per week.” Jira defaults to 8 hours per day and 5 days per week. If your organisation works different hours, update these — otherwise logged time won’t match actual working days in reports.
Yes, using the same underlying system as Jira Software. It must be enabled the same way via Settings → Issues → Time Tracking, and added to the relevant request type’s field configuration — which is a separate step from Jira Software issue type configuration.
Most “time tracking isn’t working” problems in Jira come down to three things: it’s disabled globally, it’s missing from a specific issue type’s field configuration, or the user lacks permission. Work through those in order before assuming anything more complex is wrong.
Once configuration is correct and your team logs time consistently, the data becomes useful for any reporting layer you choose — native Jira’s Time Tracking Report, JQL exports, or Report Hub‘s Timesheet view.
For how to actually log time once setup is complete, see: How to Log Time in Jira: A Complete Guide for Teams.
For everything on reporting once time is being logged, see: Jira Time Tracking: Complete Guide to Reports, Logging & Setup.
Ready to Elevate Your Jira Setup?
Partner with Grandia Solutions to unlock expert configuration, reporting, and support services — tailored to your workflows. Whether you need custom dashboards, workflow automation, or long-term consulting, our team is here to make Jira work for you.