What is a Jira Time Tracking?

The three time-tracking fields

Time tracking lives in three fields on each issue:

• Original Estimate - the initial estimate before work starts. Set once during refinement; should not be changed later (re-estimates go in Remaining).
• Remaining Estimate - the team’s current view of how much more time is needed. Updated as work progresses or scope changes.
• Time Spent - the total of all Work Log entries on the issue. Cannot be edited directly; only changes when someone adds, edits, or deletes a worklog.

A standard rule: Original is fixed; Remaining is the team’s current estimate; Time Spent is the recorded history. The three together let reports show planned vs. actual.

Time tracking vs. story points

The two systems answer different questions and aren’t mutually exclusive:

• Story points are about relative effort before work - they feed velocity and let the team forecast sprint capacity.
• Time tracking is about actual time spent during/after work - it feeds cost reports, customer billing, and post-hoc effort analysis.

Many teams use story points for capacity planning and time tracking for billing or compliance reporting (especially in JSM and consulting / agency contexts). Some teams use only one. There’s no right answer; what matters is consistency.

Configuring time tracking

Three settings to know:

1. Working hours per day (default 8) - controls how Jira expands 1d into hours.
2. Working days per week (default 5) - controls how Jira expands 1w into days.
3. Default time format - hours, days, or “pretty” (mixed 1d 4h).

Per-user format is also configurable in personal settings. Customising these to match the organisation’s actual working schedule avoids confusion when worklogs are read across timezones or fractional days.

Pitfalls

Three recurring problems:

1. Time Tracking field not on screens. Users can’t see or edit time fields; worklogs work but estimates can’t be set.
2. Original Estimate changed mid-sprint. This destroys the planned-vs-actual comparison. Use Remaining for in-flight adjustments.
3. Time logged retroactively in bulk. When a team logs all of last sprint’s time on the last day, reports look flat-then-spike. Daily worklogs (or a worklog automation reminder) keep the data useful.

Common questions

Related glossary terms

• Work Log - A work log in Jira is a single entry recording time spent on an issue by one user on a specific date, with optional comment.
• Story Estimate - A story estimate in Jira is the size assigned to a backlog item before it's worked, usually in story points but sometimes in hours, t-shirt sizes, or a custom unit.
• Story Points - Story points are a unit of relative estimation in Jira - they measure how big or complex one issue is compared to another, not how many hours it will take.