Reports feature
Planned vs Actual Report for Jira: See Which Estimates Missed and by How Much
The Planned vs Actual Report compares each Jira issue's Original Estimate with its time spent plus the time still remaining. It shows the deviation in hours and percent and marks every issue On Track, Underestimated or Overestimated against the tolerance you set, so overruns show up while the work is still open.
30-day free trial on the Atlassian Marketplace.
What Is a Planned vs Actual Report in Jira?
A planned vs actual report puts the effort you estimated next to the effort the work really took. In ActivityTimeline, planned is the Jira Original Estimate and actual is Time Spent plus Remaining Estimate, so an issue that is still open already shows where it will land. The gap is the deviation, and your acceptable deviation decides which issues need a look.
ActivityTimeline is a resource planning, capacity management and time tracking app for Jira. The Planned vs Actual Report sits in its Reports module, next to the workload, availability and utilization reports.
Reading one row: WEB-42 Address autocomplete
24h Original Estimate vs 30h Time Spent + 6h Remaining = +12h deviation, or +50%.
With a 20% acceptable deviation, WEB-42 is Underestimated. It was flagged with 6h of work still to do, not after it closed.
Planned
Jira Original Estimate
Actual
Time Spent + Remaining Estimate
Deviation
Actual minus planned, in hours and in percent
Status
On Track within your acceptable deviation, Underestimated above it, Overestimated below it
Report By
Issue, Project, Epic or Jira filter
Group By
Sprint, Project, Epic, Issue Type or a Jira field
Filters
Period, Teams, Projects, Jira filter
Output
Hours or percent, Excel export, bookmarked setup
What You Can Do with the Planned vs Actual Report
Each tile is a setting in the report. Try the drawn ones.
Decide what counts as a miss
Set the acceptable deviation. A 10% tolerance flags small slips; 25% leaves room for normal noise and shows only the issues worth a conversation.
Catch an overrun before the issue closes
Remaining Estimate counts as actual effort, so an issue turns Underestimated as soon as the work left pushes it past the estimate.
Group by epic, sprint, issue type or any Jira field
The same issues, cut the way your review needs. Grouping by a field such as Client or Component works the same way.
Roll sub-tasks into the parent, or keep them apart
Sub-task estimates and worklogs add up in the parent by default. One checkbox splits them out.
Report on a team, a project or a Jira filter
Pick teams, a period, projects or epics, or reuse a saved Jira filter that spans several projects.
Read it in hours or percent
Show Details in Percentage switches the deviation between hours and percent.
Add Jira fields as columns
When you report by issue, epic or Jira filter, add fields such as Client or Cost Center to the rows.
How to Create a Planned vs Actual Report in Jira
Three steps in ActivityTimeline. The data comes from the estimates and worklogs your Jira issues already have.
Step 1 · Choose the scope
Open Reports, then Planned vs Actual Report. Pick the period, the teams, and whether to report by issue, project, epic or a Jira filter.
Step 2 · Set the rules
Choose how to group the rows, set the acceptable deviation, and decide whether sub-task time rolls up into the parent issue. Click Apply.
Step 3 · Act on the misses
Look at the Underestimated and Overestimated rows first, open the Jira issues behind them, and bookmark or export the report for the next review.
Tip: before a review, check that worklogs are complete in Timesheets. A deviation only means something when the logged time is right.
Planned vs Actual Report in the Help CenterWhen Teams Use the Planned vs Actual Report
Six moments when estimate accuracy matters, from a single sprint to a portfolio review.
Sprint review
See which stories ran over before the retro, with the hours, so the discussion starts from data.
Quarterly estimation review
Group three months by issue type or epic to find the kind of work your team keeps underestimating.
Client and fixed-price work
Spot the epics heading past their estimate while the remaining work still leaves time to talk to the client.
Planning the next phase
Use the last phase's deviation by epic as a correction factor when you estimate similar work.
PMO review across projects
Report on a Jira filter that spans several projects and compare estimate accuracy team by team.
A new team or a new kind of work
Check after the first sprints whether the estimates hold, before the quarter's plan depends on them.
Good to know
It needs Original Estimates. Planned is the Original Estimate, so issues without one have nothing to compare against.
Actual is only as good as the worklogs. Time Spent comes from logged work, and open issues count their Remaining Estimate, so ask people to keep both up to date.
It compares time, not story points. For sprint commitments in points, pair it with your Jira sprint reports.
It works per issue, not per person and day. To compare each person's planned and logged hours day by day, use Alignment in Timesheets (below).
Can Jira Compare Estimates with Time Spent Without an App?
Partly. Jira's Time Tracking Report lists Original Estimate, Time Spent and Remaining Estimate for the issues of one project. ActivityTimeline adds a tolerance, roll-ups and a view across projects, plus two related views for trends and for people.
Built into Jira
Jira Time Tracking Report
How much time is logged and left on one project?
Lists Original Estimate, Time Spent and Remaining Estimate for the issues of one project. You compare the columns yourself.
Best for
A quick look at one project.
Reports
Planned vs Actual Report
Which estimates missed, and by how much?
Compares Original Estimate with Time Spent + Remaining Estimate across projects, and flags each issue against your tolerance.
Best for
Estimate reviews, retros and re-estimating.
Reports
Planned vs Actual Chart
Is the team planning more than it can deliver?
Shows capacity, scheduled time and logged time, week by week or month by month.
Best for
Capacity reviews and trends.
Timesheets
Alignment in Timesheets
Did each person log time the way the plan said?
Compares planned and logged hours per person and day, with colour bands by Plan Match.
Best for
Timesheet reviews and unplanned work.
Alignment view in Timesheets
"We planned 40 hours for Priya this week. How much was logged?"
Need It per Person and per Day? Use Alignment
Alignment in Timesheets puts each person's planned hours next to the hours they logged, for every day, week or month. Δ Delta shows the gap in hours; Plan Match shows logged time as a percent of planned.
The plan from Planner: estimates, bookings, placeholders and imported calendar events are the plan.
Gaps stand out: little logged against a full plan points to missing timesheets; time with no plan points to unplanned work.
Person, project or epic: the same templates as the Timeline timesheet.
Alignment Timesheets in the Help CenterScenario: compare planned and actual workAlignment for four people, 19 to 23 October. Tom logged more than planned all week; Priya logged far less, so her timesheet needs a look before the period closes. Switch between Δ Delta and Plan Match.
Planned vs Actual Report: Common Questions
Answers about comparing estimates with actual effort in ActivityTimeline. More detail in the Help Center.
Still have a question?
Contact us through the support portalFind Out Which Estimates Missed Last Sprint
Start a 30-day free trial and run the report on your own Jira issues, or see it in a 25-minute live demo with a product specialist.
30-day free trial on the Atlassian Marketplace.