Jira epic remaining work against team capacity
Atlassian’s side checked on 3 October 2026, the figures from our demo site on 10 November 2026.
An epic’s remaining work is a number of hours. Whether it lands depends on whose hours they are, and whether those people have the weeks for them. Jira keeps the two apart. This page says what Jira shows by itself, then reads one epic with Sumline and Workline.
What Jira does by itself
- 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 remaining estimate is its stories’, and nothing below them.
- No weeks. A search lists the epic’s open work items with their assignee and Remaining estimate, as one total. 60 hours due this week and 60 hours spread over a month look the same.
- No capacity. Jira’s time tracking settings give one working day and week for the whole site, with nothing for a holiday or a part-time colleague.
So Jira can say how much is left and who has it, but not whether it fits.
One epic, two answers
The example is Self-service returns, PORTAL-1, an epic with eleven stories in the Customer Portal space of our demo site, five of them done.
Workline is our app. So is Sumline. Both read what Jira already holds.
How much is left, with Sumline

- 108h remaining. Sumline adds up the epic’s stories: 307h of original estimate, 188h 15m logged, and 108h remaining, all of it in the six stories not done.
- How far along. 65% complete by story points, 45% by work item count, 5 of 11 done.
- What to check. An amber box names PORTAL-8 and PORTAL-9, past their due date, and the two done stories that went over their estimate.
Open the panel from View app actions, the hexagon under the epic’s title. Sumline is on the Atlassian Marketplace; its page on lineset.dev has more.
Who has time for it, with Workline
Apps › Workline with Rows set to Epic puts each epic’s planned hours in weeks. Open an epic for the people who hold its work, and a person for their work items. The picture under this page sorts the epics by name, so Self-service returns is the first row:
- All 108h fall in this week. Two stories are due this week, two are in the current sprint, and two are past their due date, so Workline plans those for today and names them in its amber box.
- 60h of it is Ada Isadora’s: PORTAL-4, PORTAL-5 and PORTAL-6, more than the 40h her week holds at the plan’s 8h a day, Mon–Fri. Jennifer Evans has 30h, Max Taylor 12h and Ryan Lee 6h.
To share it out, open Ada’s row in the plan by person, open the menu (⋯) of one of her work items and press Move: it lists everyone else with their hours before and after (Move work). Workline changes nothing in Jira unless you press Move or Apply (on dates for work with none).
Both apps count an estimate once: when an epic’s stories carry estimates, theirs count and the epic’s own is left out. How the plan places hours is in Jira capacity planning, and the other ways to group it in Roles and rows. Back to Workline.
