Epic rollup from a Jira CSV export

Jira does not add story points or time up to the epic. This page does it from a CSV export of your issues: each epic, and each initiative above one, with its story points, time and % complete added up from every issue under it.

The file is read on this page, in your browser. It is not uploaded, and nothing in it is kept: close the page and it is gone.

Export the issues from Jira

1. In Jira’s issue search, search for the epics and every issue under them, subtasks included. A search for whole spaces does it: project = WEB, or project in (WEB, PAY) when epics have children in other spaces.
2. Choose Export › Export CSV (all fields). Jira exports up to 10,000 issues at a time (Atlassian); for a larger search, export it in parts and drop all the files in together.
3. Drop the file below, or choose it.

How the numbers are added up

The tool follows Sumline’s rules with their default settings:

• Each estimate counted once. When a story and its subtasks both carry story points or time, the subtasks’ values are counted and the story’s own is set aside, so a story at 8 whose subtasks add up to 8 counts as 8, not 16. The row says so under Warnings.
• Logged time is added up at every level.
• Done is Jira’s Done status category, whatever the status is called.
• Remaining estimate on a done issue is not counted, and the row names the amount. Where an issue has an original estimate and no remaining estimate, its remaining is worked out as original minus logged, never below 0.
• % by estimate is story points done ÷ story points total. With no story points, it is time logged ÷ (logged + remaining). Work estimated only in the other unit adds nothing to it, so the row names it.
• % by issue count is done issues ÷ every issue under the row, at every level.
• Unestimated issues are named, not counted as 0, and a row with nothing estimated shows “—”.

What a CSV export cannot tell it

• Which story-points field a space uses. Sumline knows each space’s type from Jira: “Story Points” in company-managed spaces, “Story point estimate” in team-managed ones. The export does not say, so the tool reads, in each space, the field more of its issues have a value in, and names any issue with a value in the other one.
• Issues the file does not hold. A child in another space, or a subtask the search missed, is not counted. The tool says how many issues have a parent missing from the file.
• What changed after the export. The figures are the file’s. Sumline works them out from Jira each time you open an epic.
• Your site’s Sumline settings. In Sumline an admin can choose which level wins when both are estimated, leave fields out, add the site’s own number fields and count the remaining estimate on done issues. The tool uses the defaults (Settings).
• Times in another format. Jira exports times in seconds. A file edited in a spreadsheet may hold other values; the tool says how many it could not read and leaves them out.