Skip to content
Menu
HelpEpic progress before a release in Jira

Epic progress before a release in Jira

Jira Cloud, epics and releases. The figures from our demo site on 10 and 12 November 2026.

Jira’s own figures say how much of an epic is done. They do not say which release the done work shipped in, or how much of the epic is still to ship. This page says what Jira shows by itself, then reads one epic with Sumline and Changeline.

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 work items’, and nothing below them.
  • A release is a fix version. A work item names the release it shipped in under Fix versions. An epic has no release of its own, so the epic’s view does not say which release each done item went into.
  • No total per release. Jira adds up no estimate by release, so the done part of an epic that shipped in one release is a sum you make by hand.

One epic, two answers

Changeline is our app. So is Sumline. Both read what Jira already holds, and Changeline only reads Jira and changes nothing in it. The example is One-page checkout, an epic in our demo’s Checkout space with thirteen child work items: seven shipped in releases 1.7 and 1.8, and six are open for the next, unreleased version, Checkout 2.0.

How much is left, with Sumline

Sumline’s panel on the epic CHK-62, One-page checkout: 13 child work items across 1 level, original estimate 76h of 172h done, logged 80h, remaining 86h, complete by time 48% and by work item count 54%, 7 of 13 done, then an amber box naming CHK-28 at 113% and CHK-50 at 120% over estimate, and a table of the work items with their status, estimates and remaining time.
Sumline’s panel on the epic CHK-62, One-page checkout: 13 child work items across 1 level, original estimate 76h of 172h done, logged 80h, remaining 86h, complete by time 48% and by work item count 54%, 7 of 13 done, then an amber box naming CHK-28 at 113% and CHK-50 at 120% over estimate, and a table of the work items with their status, estimates and remaining time.
  • 76h of 172h is done. Sumline adds up the epic’s work items: 80h is logged and 86h remains, all of it in the six open items.
  • 54% by work item count, 48% by time. Seven of thirteen are done; the time view is logged over logged plus remaining.
  • What to check. The amber box names CHK-28 and CHK-50, both done and both over their estimate.

Sumline is on the Atlassian Marketplace; its page on lineset.dev has more.

When it ships, with Changeline

The picture under this page is Changeline’s panel on CHK-50. Changeline’s panel on each done item says the release it shipped in and its change lead time, split into the three stages it waited through. CHK-50 is one of the eight work items in release 1.8, and the Releases tab lists every release with its work items, the failed ones first:

Changeline’s Releases tab over Checkout and Accounts, the failed releases first: release 1.7 Checkout accessibility open to its five work items and the two failures that point at it, CHK-34 not recovered yet and CHK-140 recovered in 4d 8h, then 1.9, 2.12 and 2.10, each failed, with its reason.
Changeline’s Releases tab over Checkout and Accounts, the failed releases first: release 1.7 Checkout accessibility open to its five work items and the two failures that point at it, CHK-34 not recovered yet and CHK-140 recovered in 4d 8h, then 1.9, 2.12 and 2.10, each failed, with its reason.

Changeline counts a version only once it is marked Released, so Checkout 2.0 counts nothing until it ships. The lead time starts when a work item leaves To Do, as Lead time for changes in Jira explains, and what counts as a deployment is in What counts as a deployment. Back to Changeline.

DORA here is the research programme at Google behind deployment frequency and three other keys, not the EU’s Digital Operational Resilience Act. DORA is a trademark of Google LLC, and Changeline is not made or endorsed by Google.

Changeline’s panel on a done work item of the epic One-page checkout: shipped in Checkout 1.8 with no failure, change lead time 2.7 days, of which 21.1 hours waiting to start, 2 days in progress and 16.7 hours waiting for release.
Changeline’s panel on one shipped work item of the epic: the release it shipped in and its lead time.

Changeline is coming to the Atlassian Marketplace

Get one email the day it’s live.