How to Export a Jira Sprint Report (to Excel, and Into a Sprint Review Deck)

Jira has no export button on the sprint report itself. To get sprint data out, you export the sprint's issues from the issue navigator with a JQL filter like sprint = "Board Name Sprint 14", choosing Export CSV (all fields) or Export Excel CSV. Jira Cloud handles up to 10,000 work items per export. The report's charts, the burndown, and the completed-versus-incomplete split do not export at all: you rebuild those from the CSV.

This surprises people because the sprint report looks like a report. It has a chart, a completion summary, and neat lists of what shipped and what did not. But it is a rendered view, not a document, and Atlassian never gave it an export path. Below is the working method, the JQL that gets you exactly the sprint you mean, what each section of the report is actually telling you, and how to get from the export to the sprint review deck without spending an afternoon on it.

How to export a Jira sprint report

The reliable route is the issue navigator, not the report screen. Open your board, choose Reports from the left menu, select Sprint Report, and pick the sprint from the dropdown. Note the exact sprint name, because that is what you will filter on.

Then go to Filters, switch to JQL, and run a query scoped to that sprint:

sprint = "Payments Board Sprint 14" ORDER BY status, assignee

If sprint names repeat across boards, use the numeric sprint ID instead, which you can read off the URL of the sprint report page: sprint = 482. Once the results look right, use the Export dropdown at the top right and pick one of these:

One important gotcha: story points sometimes land in a column named after your instance's custom field rather than "Story Points," and on older instances you can get two story-point columns (one estimate, one actual). Check before you start summing.

How to export a Jira sprint report to Excel

Use Export Excel CSV (all fields) rather than plain CSV. It is still a CSV file, but Atlassian encodes it so Excel opens it directly with columns already split, which saves you the Text to Columns dance and prevents issue keys and dates from being mangled.

Once it is open, the three pivots worth building immediately are count of issues by Status, sum of Story Points by Status, and count by Assignee. Those three tables are what almost every sprint review slide is actually made of. If you want the completed-versus-carried-over split that the sprint report shows on screen, filter on resolution date falling inside the sprint window rather than trusting status alone, since a ticket can sit in Done from a previous sprint.

How many Jira issues can you export at once?

Jira Cloud supports exporting up to 10,000 work items using the asynchronous CSV export from the issue navigator. That ceiling was raised from the long-standing 1,000-issue limit in March 2025, which is why so much advice still online tells you 1,000 is the cap. For a single sprint you will never come close, but for a quarterly or release-level export you might.

Above 10,000, Atlassian's own guidance is to split the query with JQL into batches of fewer than 10,000 and merge the files by hand, noting that created date is generally the most predictable field to split on. Then verify that the total row count across your batches matches the count from the original query, so nothing is silently dropped or duplicated.

Jira sprint report explained: what each section means

Worth being precise about, because half the questions in a sprint review are really questions about how the report counts things.

Does the Jira sprint report include subtasks?

Subtasks appear in the sprint report but they are not estimated separately in the burndown when your board estimates in story points on the parent. That means a sprint can look flat on the burndown while a lot of subtask work is finishing. If your team tracks effort at the subtask level, add issuetype in subTaskIssueTypes() as a separate export and report on it alongside, rather than expecting one chart to represent both.

How do I find issues that were removed from a sprint?

The sprint report lists them under Issues Removed From Sprint, and the burndown chart's event log below the chart shows each change with the issue key, what happened, and the running story point total. That event log is the only place in native Jira where you can trace exactly when scope changed and by how much, so screenshot it or transcribe the rows before the sprint scrolls out of easy reach.

Can you export a Jira dashboard or roadmap instead?

Not usefully, and it is better to know this before you go looking. Jira dashboards have no native export at all, in any format. Every answer to this in the Atlassian community lands on the same two workarounds: print the browser page to PDF with Ctrl+P, or switch to the wallboard view and capture each gadget individually. Neither gives you data, only pixels.

Advanced Roadmaps does export, but only as .csv, through Share then Export then Export data. And it includes only the rows currently visible on your timeline once filters and view settings are applied, so set your view deliberately before exporting. A CSV of start and end dates is not a roadmap graphic, so the visual still has to be rebuilt.

From the export to the sprint review deck

This is where the time actually goes. The export takes two minutes. Turning it into something an executive audience can follow takes most people two to three hours, every sprint, forever.

A sprint review deck that works is usually six slides: what we committed to, what shipped, what did not and why, scope changes, the demo agenda, and what is next. The mistake is putting issue keys on the slides. Nobody outside the team can read PAY-4471, and a slide with 40 of them communicates nothing. Group by epic or by outcome on the slide, and keep the ticket-level detail available for the follow-up question rather than displayed by default.

Rather than screenshotting Jira gadgets into slides, which produces images that are wrong the moment a ticket moves and impossible to restyle, convert the CSV export directly into slides. Exporting Jira to PowerPoint covers the full route and what Jira does and does not give you at each step. The counts by status, epic, or assignee come back as native editable chart objects rebuilt from your data, so when someone challenges a number you can fix it on the slide instead of going back to Jira. Ticket-level detail goes into speaker notes cited to the source row, which is exactly where the answer to the follow-up question belongs. If your export is a workbook, Excel to PowerPoint is the direct path; if you print the sprint report to PDF, use PDF to PowerPoint; and a written sprint summary you already send by email goes through text to presentation.

The structural fix that saves the most time is making the deck a template, not a document. Load your brand template once and every sprint's export comes back in the same fonts, colors, and slide order, so the only thing that changes between sprints is the content. Teams running the same readout at a quarterly cadence should look at the QBR deck and executive briefing patterns, and anyone with the same problem one layer up in the reporting stack will recognize it in Power BI to PowerPoint.

A note on why the carryover number keeps embarrassing people

Chronic carryover almost never means the team is slow. It usually means work was accepted into the sprint that was never sized, or that tickets sat unassigned for the first three days because nobody decided who owned them. If that is the pattern in your export, the useful intervention is upstream of the report: getting incoming work routed to the right owner automatically the moment it arrives removes the quiet two-day gap that shows up later as an unfinishable sprint. No amount of better reporting fixes a queue nobody picked up.

That is also the honest framing for the report itself. The sprint report is a mirror. Exporting it faster, and presenting it clearly, gets you a much better conversation about what the mirror is showing, which is the whole point of the review.

Quick reference