Jira Cloud Time Tracking: Estimates, Work Logs & Reports

Jira Cloud time tracking lets you estimate how long work will take, log the time you actually spend, and turn both into reports for planning and billing. You enter estimates and work logs on issues, and Jira’s built-in reports and dashboards summarize them per assignee, project, or sprint.

Formula

The core calculation is simple: Remaining estimate = Original estimate − Time spent. In Jira, the original estimate is the number of hours or days you set when you create or plan an issue. Time spent is the sum of all work logs added to that issue. Progress is the percentage of the original estimate that has been logged: (Time spent ÷ Original estimate) × 100.

• Original estimate (t) – the initial time you expect the task to take, in hours.
• Time spent (l) – the total logged time, in hours.
• Remaining estimate – what’s left to do, in hours.
• Progress – a percentage showing how much of the estimate has been logged.

Worked Example

Using the defaults: original estimate = 8 hours, time spent = 6 hours.

1. Remaining estimate = 8 − 6 = 2 hours.
2. Progress = (6 ÷ 8) × 100 = 75%.

So after logging 6 hours on an 8-hour estimate, Jira shows 2 hours remaining and 75% progress. The same math applies to every issue, and Jira rolls these numbers up into sprint and version reports.

How Jira Cloud Time Tracking Works

Jira Cloud includes time tracking as a built-in feature, but it’s not enabled by default on every project. An administrator must turn it on in the project’s settings under Features. Once enabled, each issue shows three fields: Original Estimate, Time Spent, and Remaining Estimate. You can set the estimate when creating an issue or later, and you log time via the “Log work� button on the issue view.

Work logs can include a description, a date, and a time spent value. By default, Jira subtracts the logged time from the remaining estimate automatically. If you want to change the remaining estimate manually, you can edit it directly, but that breaks the automatic link. Jira also lets you set the time unit (hours or days) and the number of hours per day (usually 8) in the global time tracking settings.

Reports Built Into Jira Cloud

Jira Cloud provides several reports that use time tracking data:

• Time Tracking Report – shows original estimate, time spent, and remaining estimate per issue, grouped by assignee or component.
• Workload Report – displays the remaining estimate per assignee, helping you see who is overloaded.
• Version Workload Report – similar, but broken down by fix version.
• Sprint Report – shows completed vs. incomplete work in a sprint, including time spent per issue.
• Burndown Chart – plots remaining estimate over time, based on logged work.

These reports are available under Reports in the project sidebar. They read directly from the issue fields, so if time tracking is not enabled or no one logs time, the reports will be empty.

Common Problems and Misconceptions

One frequent issue is that time tracking is not enabled, so the fields don’t appear. Another is that users log time but forget to set an original estimate, making the remaining estimate meaningless. A third is that Jira’s default time tracking only counts work logs, not calendar time – so a task that spans a week but has 2 hours logged shows only 2 hours spent.

A common misconception is that Jira’s reports show billable hours. They don’t. They show whatever time people log, with no distinction between billable and non-billable work. To get billable hours, you need a third-party app like Tempo Timesheets or Timebudget, which add cost rates and approval workflows.

Another problem is that editing the remaining estimate manually can cause the burndown chart to jump unexpectedly. If you want the chart to reflect only logged work, leave the remaining estimate alone and let Jira calculate it.

Choosing a Time Tracking Method

For small teams, Jira’s built-in tracking is often enough. You get estimates, work logs, and basic reports without extra cost. For larger teams or those needing billing, invoicing, or detailed timesheets, a marketplace app is worth considering. Popular options include Tempo Timesheets (cost tracking, approvals), Timebudget (budget vs. actual), and Everhour (time tracking with project budgets).

Before choosing, ask:

• Do you need to track time against customers or projects for billing?
• Do you need approval workflows for timesheets?
• Do you need integrations with accounting or payroll tools?
• Do you need mobile time tracking with offline support?

If the answer to any of these is yes, a paid add-on likely fits better than the built-in feature.

Costs and Limits of Built-in Tracking

Jira Cloud’s built-in time tracking is free – it’s part of every plan, including the free tier. There’s no per-user fee for the feature itself. However, the free plan limits you to 10 users and 2 GB of storage, which may be a constraint for larger teams. Marketplace apps are paid separately, usually per user per month, and pricing varies widely.

One limitation of the built-in feature is that it tracks only time, not costs. It also lacks a way to lock or approve work logs. If you need those, you’ll need an app. Another limitation is that the reports are basic – they don’t allow custom date ranges or advanced filtering beyond what the report itself offers.

Alternatives to Jira’s Native Time Tracking

If you find Jira’s built-in tracking too limited, there are several paths:

• Marketplace apps – Tempo Timesheets, Timebudget, Everhour, Clockwork, and others add features like approvals, cost rates, and detailed reports.
• External time trackers – Tools like Toggl Track, Harvest, or Clockify can be used separately, then you manually copy totals into Jira (or use integrations that sync).
• Manual spreadsheets – Some teams track time in Excel or Google Sheets and only update Jira with final numbers. This is simple but error-prone and lacks real-time visibility.

Each alternative has trade-offs. Marketplace apps keep everything in Jira but add cost. External trackers are often cheaper but require syncing. Spreadsheets are free but manual. The right choice depends on your team’s size, budget, and need for billing or compliance.

Frequently Asked Questions

Why don’t I see time tracking fields in my Jira project?

Time tracking must be enabled by a project administrator. Go to Project Settings → Features and turn on “Time tracking.� If it’s already on, check that you’re looking at an issue type that supports time tracking (most standard types do).

Can I log time for someone else?

Yes, if you have the “Work On Issues� permission and the “Edit Work Logs� permission, you can log time on any issue, including for another user. The work log will show the actual author as the person who logged it, but the time is attributed to the issue, not to a specific user unless you set the “User� field in the log work dialog.

How do I change the original estimate after I’ve started working?

You can edit the Original Estimate field directly on the issue, just like any other field. However, changing it will recalculate the remaining estimate based on the new original minus time spent. If you want to keep the current remaining estimate, you may need to adjust the original estimate accordingly.

Does Jira Cloud track time automatically?

No. Jira does not start a timer or track your activity automatically. You must manually log time using the “Log work� button. Some third-party apps offer automatic tracking, but the native feature is manual.

Can I export time tracking data to Excel?

Yes. You can export the Time Tracking Report or the Workload Report to CSV or Excel using the export options in the report view. You can also use Jira’s REST API to pull worklog data programmatically.

What happens if I log more time than the original estimate?

The remaining estimate becomes negative. Jira allows this, and it shows as a negative number. The progress percentage will exceed 100%. This is useful to flag that a task took longer than planned, but it can skew burndown charts if you don’t update the estimate.

Related

• Android Backup with Broken Screen: How to Do It
• Rocket League Icons and Symbols: Complete Guide
• Steam Deck Offline Game Pass: SteamOS vs Windows

in t | Estimated hours | h | 8 | 0
in l | Logged hours | h | 6 | 0
out remaining | Remaining estimate | h | t - l | 2
out progress | Progress | % | (l / t) * 100 | 1