How to roll up epic dates & progress in Jira (free)
Here's a problem every Jira project manager knows: you set an epic to finish at the end of the month, the stories underneath it slip a fortnight, and the epic's due date doesn't move. Report off the epic and you're reporting fiction — the parent and its children have quietly drifted apart. This guide shows how to roll up epic dates and percent-complete from the work underneath, automatically, in Jira Cloud, for free.
What "rollup" means
Rollup is when a parent issue's schedule is derived from its children instead of typed in by hand:
- Start date = the earliest start of any child.
- Due date = the latest end of any child.
- % complete = the progress of the children, weighted by how long each one is (a three-week story should count for more than a one-day chore).
Done properly it's bottom-up: sub-tasks roll into their story, stories roll into their epic. Each level reflects everything beneath it, so the top of your plan is always honest.
Why Jira doesn't do this on its own
In native Jira, an epic's start and due dates are just fields — nobody recalculates them when a child moves. Jira Premium's Advanced Roadmaps can roll dates up, but it's a heavy, Premium-tier tool if all you actually want is parent dates that stay in sync. For most teams the gap is filled by a Marketplace Gantt app that treats the parent bar as a summary of its children.
How to roll up epics in Jira (step by step)
- Install a free Gantt app with rollup. Open the GanttBoard listing and click Get it now (you need Jira admin). It's a Forge app, so your project data never leaves your Atlassian tenant.
- Open a project → the GanttBoard tab. Your epics, stories and sub-tasks appear on the timeline in their natural hierarchy.
- Nothing to configure. Every parent with children automatically draws a slim summary bar spanning its earliest child's start to its latest child's end, with a duration-weighted % complete shown above it.
- Drag the work underneath. Reschedule or resize a child and the parent bar reshapes itself instantly. Summary bars are read-only on purpose — they reflect the children, so a derived date can never overwrite the real issue dates in Jira.
How to read a summary bar
The summary bar tells you, at a glance, the true span and health of an epic. A short progress fill on a bar that stretches well past today is your early warning that an epic is behind — long before anyone opens the individual stories. Pair it with critical-path highlighting to see which child is dragging the date, and a baseline to see how far the epic has drifted from the original plan.
A worked example
Say an epic has three stories: a 2-day spike (100% done), a 10-day build (50% done) and a 4-day test pass (0% done). Hand-typed, the epic might still say "due last Friday." Rolled up, the epic now spans from the spike's start to the test's end, and its progress is the duration-weighted average — roughly 39%, not the 50% you'd get from a naive "average of the three." That weighting is what keeps the number trustworthy when child durations differ.
The short version
Jira won't keep epic dates and progress in sync with the work inside them — but adding automatic rollup is free and takes no setup: install a Forge Gantt app, open your project, and every parent becomes a live summary of its children. From "the epic said we were fine" to a timeline you can actually report off.