The Planned vs. Tracked report helps you compare how much time was estimated for tasks against how much was actually spent. Use it to spot estimation gaps, identify tasks that took longer than expected, and improve your future planning accuracy.
Report columns
The report table includes the following columns. You can show or hide optional columns in the report settings.
Shown by default:
Work item — Jira issue name and key
Epic — the epic this work item belongs to
Status — current Jira issue status
Space — Jira space containing the issue
Start date and Due date — scheduled dates for the work item
Assignee — team member assigned to the issue
Planned time — total estimated time (see how it’s calculated below)
Tracked time — total time logged via work log entries
Remaining — hours still expected to complete the task
Deviation — difference between actual and planned time (in hours)
Deviation % — actual effort vs. plan (percentage)
Hidden by default (can be enabled):
Team — Jira team assigned to the issue.
Story points (hours) — Story points + hour equivalent (e.g.,
3 (24h)). Conversion rate defined in settings.Original estimate — Original Estimate value from Jira.
How Planned time is calculated
Planned time represents the total estimated effort for a work item. It equals the task’s own time estimate plus the estimates of all its parts (if any).
Planned time = Time estimate + Parts estimate
Your estimation settings control how the time estimate is calculated:
Internal estimation mode — uses the time estimate set directly in Planyway.
Synced with Story Points — story points are converted into hours based on your configured conversion rate, and that value is used as the time estimate.
Synced with Remaining — the time estimate is taken from the Original Estimate field in Jira. The Remaining value in this case is counted toward actual time (Tracked + Remaining), not toward planned time.
If a work item has Parts, their estimates are added to the parent’s Planned time. In other words, the parent’s Planned time is the sum of its own estimate and all its parts’ estimates.
Tip: Hover over the (?) icon in the Planned time column header to see how the value is calculated.
How Deviation is calculated
Deviation shows the difference between the actual effort and the plan:
Deviation (h) = Actual time − Planned time
* where Actual time = Tracked time + Remaining time
The deviation value uses color coding and signs to make it easy to interpret at a glance:
Scenario | What it means | Display |
Planned > Actual | You overestimated — the task required less effort than planned | Black text, negative value (e.g., −4h) |
Planned < Actual | You underestimated — the task took more effort than planned | Red text, positive value (e.g., +6h) |
Planned = Actual | The estimate was accurate | Black text, 0h |
Note: If Actual time is 0 (no time tracked or remaining), the deviation will be negative (overestimated). If Planned time is 0 (no estimate set), the deviation will be positive and shown in red (underestimated).
How Deviation % is calculated
Deviation % shows actual effort as a percentage of the plan:
Deviation % = (Tracked time + Remaining time) / Planned time × 100
For example:
80% means the team used 80% of the estimated time — they came in under the estimate.
100% means actual effort matched the plan exactly.
130% means the task took 30% more effort than originally planned.
The progress bar in the Deviation % column reflects these three states visually, using the same color logic as Deviation.
Tip: Hover over the (i) icon in the Deviation % column header to see the formula.
Tooltip states on the progress bar
When you hover over the Deviation % progress bar, a tooltip appears showing the breakdown. The tooltip reflects one of three states:
Planned > Actual — task is under budget, shows remaining capacity.
Planned < Actual — task exceeded the estimate, highlighted as overrun.
Planned = Actual — estimate and actual effort match perfectly.
Report settings
Use the gear icon in the report to customize the view:
Include subtask time into parent work items — rolls up tracked time from subtasks into parent issue totals. Subtasks still appear as separate rows with their own time data.
Include parts time into parent work items — rolls up tracked time from parts into parent issue totals.
You can also filter by projects, team members, epics, and set a custom date range — just like in other Planyway reports.
Export
The Planned vs. Tracked report can be exported to Excel or CSV with all your current filters and sorting preserved.