Estimate vs time logged on a Jira epic, by person

An epic runs over its estimate, and Jira shows a total with nothing behind it: no person, no week. Two questions follow. How far over is it, and whose hours were they? On Atlassian Community it reads “we are looking for options to check how much effort in one epic or story has been spent for a month” (Community, June 2026). This page says what Jira adds up by itself, then answers both questions on one epic, with Sumline for the estimate and Logline for the people.

What Jira does by itself

• Time spent on a work item is every worklog on that work item, from any date and by anyone. It leaves out the work item’s children.
• Σ Time Spent adds a work item’s sub-tasks to its own time. On an epic in a company-managed space it does not add the epic’s stories; the request to change that, JSWCLOUD-18871, has been open since 2020.
• The work item view adds time one level up the hierarchy. Atlassian’s note of 3 June 2025 on JRACLOUD-70150 says rolling up “doesn’t go beyond that”, so the time on the sub-tasks under an epic’s stories does not reach the epic.
• Who logged it is on each work item’s Work log tab, one work item at a time. Nothing adds the people up across an epic and its stories.

So the epic’s time and its estimate can be read, a level at a time. Who spent it, and when, means opening every story and adding by hand.

The estimate against the hours, with Sumline

Sumline is our app. Its panel on an epic adds up original estimate, time spent and remaining across every level below it, and sets them side by side. The example is Q4 storefront, an epic with four stories in the Harbor Labs space of our demo site:

• The totals. Original estimate 592h, time spent 470h 30m, remaining estimate 123h 30m, and 79% complete by time: logged ÷ (logged + remaining).
• One estimate counted once. The epic carries 80h of its own, and its stories carry their own. Children win, so the epic’s 80h is left out and the box says so.
• Each story’s own figures are the table: original estimate, logged and remaining per story, so the story that went over stands out. Here it is HLAB-2, Checkout redesign: 14h logged against 12h, marked “1 over estimate”.

Open the panel from View app actions, the hexagon under the work item’s title. Sumline is on the Atlassian Marketplace.

Who logged them, and when, with Logline

Logline is our app too. Its panel on the same epic reads the same worklogs, from the epic and its child work items, and splits them by person and by week:

• The first line sets the hours against the estimate, using the stories’ estimates as Sumline does: 470.5h logged of 592h, 121.5h under. It differs from Sumline’s 123h 30m remaining by 2h, what HLAB-2 went over its estimate: its remaining is 0m, not −2h.
• Who logged time lists each person’s hours, their share as a bar and the day they last logged: Kevin Campbell 125h, Alana Grant 116h, Mitch Davis 116h and Cassi Owens 113.5h.
• Time logged per week is one bar for each of the last 8 weeks, named by the day the week starts, so the weeks the hours went in show.

Open in Logline opens the report on the epic and its children, with each worklog and its comment. Logline is not on the Marketplace yet; its page on lineset.dev has the waitlist.

Sumline and Logline only read what Jira holds. How Sumline counts each field is in How the numbers are calculated; how time on sub-tasks reaches the epic is in Roll up logged time to the epic in Jira. More on the Sumline home page.