Epic Progress Rollup for Jira
Know where every epic stands without counting by hand.
Epic progress is usually estimated in a meeting or counted by hand in a spreadsheet. Epic Progress Rollup calculates it from the child issues themselves and keeps it current as work changes.
ACME-42
ACME-61Retry queue backoff24 points remaining across 11 issues
Illustrative preview · Example data
Epic progress is guesswork until someone counts by hand.
Jira shows you the issues inside an epic, but not how far along the epic actually is. Delivery leads end up exporting lists, counting statuses or maintaining a spreadsheet that is out of date by the next standup.
The people who feel it most are the ones asked for a number: engineering managers, product managers and program leads reporting upward on work they cannot see at a glance.
Best for
- Delivery leads
- Engineering managers
- Product managers
- Program managers
Live progress on every epic, with no manual rollups.
Progress bars sit on the epic itself and recalculate within seconds when a child issue changes. A dashboard gadget rolls up to 50 epics per page with JQL filtering, so reporting uses the same live numbers the team sees.
Three steps from setup to result.
Open any epic
The progress panel shows completion by status category, story points or time tracking, calculated from the epic's child issues.
Choose the metric that fits
Switch between status categories, story points and time tracking so the number matches how your team estimates.
Report from a dashboard
Add the gadget to a Jira dashboard and filter up to 50 epics per page with JQL, the same live data, at portfolio level.
What this app helps your team do.
Three metric types
Track completion by status categories, story points or time tracking, per epic.
Event-driven recalculation
Progress updates within seconds of child-issue changes; no scheduled jobs, no stale figures.
Dashboard reporting
A Jira dashboard gadget with JQL filtering rolls up to 50 epics per page.
No manual rollups
No spreadsheets or scripts to maintain; the numbers come from the issues themselves.
Limits and requirements, explained upfront.
- Jira Cloud only; no Data Center or Server support.
- Progress reflects the issues linked under each epic; work tracked outside the epic hierarchy is not counted.
- The dashboard gadget shows up to 50 epics per page.
What setup and ongoing management look like.
Once the listing is live, a Jira admin installs the app from the marketplace; no per-project configuration is required to start seeing progress. Gadget settings (metric, JQL filter and epic selection) can be changed at any time. Uninstalling removes the app and its Forge storage; no progress data is written back to issues, so nothing in Jira needs cleanup.
What the app can access, and why.
Check the app's runtime, permissions, storage and external connections before enabling it. These details are specific to this app.
Epic Progress Rollup runs on Atlassian Forge with zero external network egress; computation and storage stay inside your Atlassian cloud tenant.
- Runs on
- Atlassian Forge; the app runs inside Atlassian's cloud platform.
- Reads
- Issue data (epics and their child issues) through Forge APIs.
- Can change
- No Jira issue data. Progress values are calculated and stored by the app, not written back to issues.
- Stores
- Calculated progress data and dashboard gadget configuration.
- Storage location
- Forge storage inside your Atlassian cloud tenant.
- External connections
- None; zero external network egress.
- Data retention
- Progress data is recalculated from current issue data; stored values are removed when the app is uninstalled and its Forge storage is deleted.
- AI use
- None.
Pricing will appear with the marketplace listing.
This app is not yet publicly available. Current pricing and billing terms will appear here after its marketplace listing is live.
Support from the people responsible for the app.
Tell us which app you're using, where the issue occurred, what you expected and what happened instead. We aim to respond within two Australian business days.