JIRA Time Tracking
Teams plan better when they know how long work takes. JIRA time tracking records three numbers on every issue: the estimate, the time spent, and the time remaining. The numbers help teams forecast, budget, and learn from past work.
The Three Time Fields
Time Tracking Fields
| Field | Meaning | Sample Value |
|---|---|---|
| Original Estimate | The planned effort before work starts | 8h |
| Time Spent | The total effort logged so far | 5h |
| Remaining Estimate | The effort left to finish | 3h |
Layman's View: A Fuel Gauge
A driver plans a trip that needs a full tank. The plan equals the original estimate. Fuel burned on the road equals time spent. Fuel left in the tank equals the remaining estimate. A glance at the gauge tells the driver whether the trip stays on track.
Original Estimate : 8h [########] Time Spent : 5h [#####...] Remaining : 3h [.....###]
Time Format
JIRA reads short codes for time entries. Letters stand for weeks, days, hours, and minutes.
Time Entry Formats
| Entry | Meaning |
|---|---|
| 30m | Thirty minutes |
| 2h | Two hours |
| 1d 4h | One day and four hours |
| 1w 2d | One week and two days |
Default settings count a day as 8 hours and a week as 5 days. Administrators can change these values to match local working hours.
Logging Work
- Open the issue.
- Select the option to log work.
- Type the time spent, such as 2h.
- Pick the date and time the work started.
- Choose how JIRA should update the remaining estimate.
- Add a short comment about the work and save.
Remaining Estimate Options
How Logging Adjusts the Remaining Time
| Option | Result |
|---|---|
| Adjust Automatically | JIRA subtracts the logged time from the remaining estimate |
| Leave Existing Estimate | The remaining estimate stays unchanged |
| Set to a New Value | The person types a fresh remaining estimate |
| Reduce by a Set Amount | JIRA subtracts a custom amount from the remaining estimate |
Time Tracking and Story Points
Scrum teams often estimate with story points. Story points measure relative size, such as small, medium, or large. Time tracking measures hours. Some teams use only points for planning and add hours for client billing. Other teams use hours alone. Pick the method that answers the questions your organization asks.
Example: Three Days on One Issue
A developer estimates a report page at 12 hours. The log shows how the numbers change.
Work Log for Issue WEB-45
| Day | Time Logged | Total Spent | Remaining |
|---|---|---|---|
| Monday | 4h | 4h | 8h |
| Tuesday | 5h | 9h | 3h |
| Wednesday | 4h | 13h | 0h |
The final total of 13 hours beats the estimate by one hour. The team notes the gap and adjusts the next estimate.
Reports That Use Time Data
Logged time feeds reports that compare estimates against reality. Available reports vary by JIRA plan and add-ons. Project managers use them to spot tasks that regularly run over, and finance teams use them to prepare client invoices.
Good Habits
- Log time at the end of each day while memory stays fresh.
- Update the remaining estimate honestly. A stale number misleads the whole team.
- Use logged data to improve future estimates, and avoid using it to rank individuals.
- Agree on one rule for what counts as work, such as including meetings or skipping them.
Summary
Time tracking rests on three fields: original estimate, time spent, and remaining estimate. Short codes like 2h and 1d 4h speed up entry. Work logs build a history that sharpens future planning. Daily logging and honest updates keep the numbers trustworthy.