Jira planned vs actual hours, by epic
Atlassian’s side checked on 3 October 2026, the figures from our demo site on 10 November 2026.
Planned against actual is two questions about the same work: where did the hours go, and where are they going next? Jira holds the answer to both, one work item at a time. This page says what Jira shows by itself, then reads two spaces by epic, the four weeks behind with Logline and the four weeks ahead with Workline.
What Jira does by itself
- One work item at a time. A work item shows its Time spent beside its Remaining estimate, so its own planned and actual sit side by side.
- Time adds up one level. Atlassian’s note of 3 June 2025 on JRACLOUD-70150 says rolling up “doesn’t go beyond that”, so an epic’s hours are its stories’, and nothing below them.
- No weeks. Neither the hours logged nor the hours left are put in weeks, and the time tracking settings give one working week for the whole site.
So Jira can say what each work item took and has left, but not which epics took the last month, or which take the next.
Two spaces, two directions
The example is the Customer Portal and Portal mobile app spaces of our demo site, PORTAL and MOBILE, with six epics between them.
Workline is our app. So is Logline. Both read what Jira already holds, and both group the work by epic here: the work, not the people.
The four weeks behind, with Logline

- 784h in four weeks, from 145 worklogs, between 188h and 206h a week.
- Mobile checkout took the most, 197h 15m, almost all of it in the last two weeks. Self-service returns took 158h 15m and Order tracking 154h 45m.
- Each work item opens to its worklogs: the day, who wrote it, the hours and the comment.
Under Apps › Logline, set Rows to Epic, Then by to Work item and Per to Week. Logline is on the Atlassian Marketplace; its page on lineset.dev has more.
The four weeks ahead, with Workline
Apps › Workline over the same two spaces, with Rows set to Epic and Weeks to 4 weeks, puts each epic’s remaining estimates in the weeks ahead (the picture under this page):
- 526h planned over the four weeks, 167h of it this week.
- Order tracking leads, 164h, opened in the picture to the people who hold it and Emma Paris’s two work items. Mobile checkout, last month’s biggest, has 78h left.
- Self-service returns took 158h 15m behind and has 108h ahead, all of it planned for this week.
Workline changes nothing in Jira unless you press Move or Apply (on dates for work with none). How it places the hours is in Jira capacity planning, and the other ways to group the plan in Roles and rows. Back to Workline.
