Export epic progress from Jira to Excel or CSV

You report on epics outside Jira, in a spreadsheet or a slide, and you want each epic’s progress in the export. On Atlassian Community it reads “How can I include Epic progress (% of completed issues) when exporting reports from Jira?” This page says why the export leaves it out, the two ways to get it into the file with Jira’s own tools, then what Sumline downloads.

Why the export leaves it out

The % done on an epic is not a field. Atlassian declined to turn the child work items’ progress into a field you can search, export or report on (JRACLOUD-80273, “Won’t Do”, August 2024). An export holds fields, so it is not there.
Story points do not add up to the epic at all (JRACLOUD-90636, “Not Being Considered”), so an epic’s own Story Points column is empty or holds whatever someone typed.
Time adds up one level. The Σ time tracking columns export, in seconds, and an epic’s include its stories’ own time but not their subtasks’ (JRACLOUD-70150).

Work it out in the spreadsheet (free)

Search for the epics’ children, for example parent in (ABC-1, ABC-2, ABC-3).
Add the columns Parent, Status and Story Points (in team-managed spaces, Story point estimate).
Export to CSV (Atlassian).
In the spreadsheet, per parent: the rows in your done statuses ÷ all its rows gives % by count; the points of those done rows ÷ all its points gives % by points.

It is accurate for the moment you export, one level deep: subtasks need a second search and a decision about which level counts.

Or write it into fields first

An Automation rule can keep each epic’s % done in two number fields, which then export like any other column. The rule and Atlassian’s two formulas are in Jira epic % complete by points and by issue count. The fields are only as current as the rule’s last run, and the rule counts direct children only.

With Sumline

Sumline is our app. Its tables download as Excel or CSV, one row per epic, with the figures already worked out:

Both percentages, by estimate and by issue count across every level below, beside story points done / total, original estimate, time spent and remaining, status, assignee and priority.
The rows you see: the table’s own rows in its current filter and sort, from one space or across the spaces you choose, with a Space column in the downloads.
What was left out is in the file too: the downloads note the values the mixed-estimate rule set aside and any remaining time on done issues not counted.
Numbers stay numbers in Excel: story points, percentages and counts add up; a missing estimate is an empty cell, never 0.

Sumline only reads, so its figures are in the table and the files, not in fields in Jira. What each column holds is in Excel and CSV export.