Jira has no native report that shows % done, % in progress, and % not started under an Epic — and the gap isn’t new. Community threads asking for it run from 2019 through a fresh one posted in February 2026, and every accepted answer lands on the same three non-answers: a manual custom field, a hand-built automation rule, or a Premium-gated bar that Atlassian’s own documentation admits undercounts the hierarchy by design. Jira’s Epic panel will show that one Epic’s own progress bar — but there’s no built-in way to see the same number for every Epic in a project at once, let alone break it into the three buckets (“done,” “in progress,” “not started”) that a status report actually needs.
Does Jira have a native percent-complete report by Epic?
No, and two Community Champions have said so directly, a year apart. Someone asked for a report showing ”% completed for an epic based on how many Stories/Bugs issues linked to that epic are completed = done,” and the accepted answer was blunt: “That type of report is not available natively in Jira Cloud except when you are looking at the details of an individual Epic.” Nine months earlier, someone asking almost the identical question — a dashboard showing “the percentage of completed tasks for each Epic” — got the same wall from the same Champion: “There is no native way in Jira to show the percent done for an epic in a dashboard” (Community thread).
Jira does show a progress bar — but only on the single Epic you’re currently viewing, computed from its own direct children, and only in that one panel. There’s no dashboard gadget, no report, and no list view that shows the same reading for every Epic in a project side by side.
What people build instead
Three routes recur across the threads, and none of them is a checkbox in Jira settings:
- A dashboard gadget on a saved filter. The Issue Statistics gadget, pointed at a filter like
project = XXX AND Sprint in openSprints(), gives a real status breakdown with percentages — free, native, and the oldest of these threads (2019) landed here. It’s scoped to whatever filter you built, though, not an Epic-by-Epic report; you get one bar for the whole filter, not one row per Epic. - A hand-built Automation rule. The recurring DIY pattern: trigger on a schedule or status change, run a Lookup Issues action against the Epic’s children, divide done by total, and write the result into a custom “Percent Complete” field. This exact recipe shows up, rebuilt from scratch, in a February 2026 thread — proof the gap is still open seven years after the first thread asking for it, not a problem Jira quietly fixed along the way.
- A Marketplace app. Respondents across these threads name specific apps for exactly this — AIO Reports and Timesheets (percent complete against a custom category field, in a 2020 thread), Issue Hierarchy, and eazyBI (both named directly in the 2026 thread above). Each is a separate purchase and a separate thing to configure and maintain.
Does Jira Premium’s Advanced Roadmaps (Plans) fix this?
Partly — and Atlassian’s own documentation flags the part that doesn’t work the way people expect. Plans (Premium and Enterprise only, confirmed here) can show a rolled-up progress bar on a parent issue. But the default version of that bar — Progress by issue count — has a documented, intentional limitation: per Atlassian’s own knowledge-base article, it “does not take into account the issues nested beneath it. Instead it shows the completion for the next level” down only.
Atlassian’s own worked example makes the size of the miss concrete: an Initiative with one Epic fully broken into 10 done stories, and a second Epic never broken down at all, reads as 50% complete on that bar (one Epic done, one open) — when the real hierarchy, all 11 leaf issues counted, is 92% done. A Community thread from January 2023 ran into this directly, asking how to roll Story-level progress up to the Initiative level. The answer from a Community Champion: the Progress field “appears to be limited to the direct child issues,” with no setting found to change the basis.
Atlassian’s own fix for this is to switch the bar to “Progress based on estimates” — weighting by story points or hours instead of counting issues. That’s real, and it’s the right instinct. But it still produces one blended number, still lives inside that one Plan’s timeline, and still requires a Premium or Enterprise seat to see at all.
Can I roll percent complete up to an Initiative, not just an Epic?
Rarely, and mostly unanswered. A thread titled plainly “Initiative Percent Complete Field” asked whether any field could show this at the Initiative level — “preferred” — or failing that, the Epic level. It sat with zero replies. Combined with the direct-children limitation above (an Initiative’s Progress field counts Epics, not the Stories two levels down), getting a real story-level rollup at the Initiative tier means going outside both native Jira and Plans entirely.
The honest summary
| Path | Shows all 3 buckets (done / in progress / not started)? | Rolls up past direct children? | Cost |
|---|---|---|---|
| Epic’s own progress panel | No — one blended % | N/A (single Epic only) | Free |
| Dashboard gadget on a filter | Partial — status breakdown, not per-Epic | No — one bar per filter | Free |
| Automation rule + custom field | No — you compute one % | Only as far as your JQL reaches | Free, but brittle and rebuilt by hand each time |
| Advanced Roadmaps (Plans) rolled-up bar | No — one blended % | No — direct children only, by Atlassian’s own design | Premium/Enterprise seat |
| Marketplace app | Varies by app | Varies by app | Separate purchase |
If you came here expecting a Jira setting labelled “percent complete,” there isn’t one — every real path above is either a number you compute yourself, a view scoped to one Epic or one filter, or a paid seat that still stops at the level directly beneath the row you’re looking at.
What OneView does instead
OneView has a Progress column built to the shape these threads keep asking for, spec’d directly by a paying customer (City of Surrey) who put it plainly: “progress reported in both story points and/or # of work items, including the % complete, % in progress, and % not started… progress of the initiative should be based on all the stories underneath it.” That’s three shares, not one number — because a row reading “70%” can’t say whether the other 30% is in flight or untouched, and that’s the actual question a status report gets asked.
The buckets are drawn straight from the statuses already in Jira: To Do, In Progress, and Done map directly, and a Blocked issue counts as in progress rather than not started, on the reasoning that it’s work that started and stalled, not work nobody’s touched — a real modeling choice, not a default nobody thought about. You can weight the rollup by story points or by raw item count (the community’s own preference, when only one is possible, runs toward item count), and it counts every descendant issue in the hierarchy below whatever row you’re looking at — not just direct children — so an Initiative’s Progress reflects the Stories two levels down, the exact gap the “Initiative Percent Complete Field” thread above got zero answers on. It works the same way across both Jira and Microsoft Planner data. Start a free trial and add Progress to a grid grouped by Epic or Initiative to see it against your own hierarchy.
Related reading
This page is about a status percentage — how much of an Epic or Initiative’s underlying work is actually done, broken into three real buckets. Two related but different questions live on their own pages: if what you need is a single number rolled up to a parent (a raw Story Points total, not a status split), see sum story points from children to a parent in Jira — same missing-rollup problem, a different field. And if the question isn’t “how done is this Epic” but “who’s overloaded,” see Jira capacity planning across projects — a per-person load reading, not a per-Epic completion one. Same underlying shape (Jira doesn’t roll values up across issues on its own), three different axes people search it from.