Jira has no native Excel export any more — it hasn’t since 2016 — and the CSV export that replaced it is, in the words of a longtime Atlassian Community moderator, “not a viable replacement for the Excel export.” On top of the format problem, there’s a real item-count ceiling: 1,000 issues on the older export path, up to 10,000 on Jira Cloud’s newer asynchronous export — and nothing in Jira’s own documentation describes a clear warning when your export quietly stops short of your filter’s real result count. Here’s what Jira’s export can and can’t do today, and how to get a real spreadsheet out of it anyway.
Why doesn’t Jira export straight to Excel any more?
Because it never really did. Before Jira Server 7.2 (2016), what Jira called “Export to Excel” was actually an HTML file saved with an .xls extension — a trick that worked until a Microsoft security update started blocking Office from opening files disguised that way. Atlassian’s own explanation at the time, quoted by a community champion on the Atlassian Community forum: “We removed the Excel export option in JIRA 7.2, as we’ve introduced a more robust, flexible exporter in the CSV export.” CSV became the only native format, and it still is — in Cloud and in Server/Data Center alike.
Users pushed back immediately, and the pushback never really stopped. On that same thread, Atlassian Community moderator Nic Brough put the consensus plainly: “The CSV exporter is not robust or flexible, and the clear consensus from users is that it is not a viable replacement for the Excel export.” Specific complaints from the JIRA 7.2.x Excel export gone? thread: fields containing commas “can no longer export sensibly,” and the old Excel export’s clickable hyperlink back to each issue disappeared — CSV is plain text, so there’s no link to click. Nearly a decade later, that’s still the honest state of native Jira export: a CSV file, not a spreadsheet.
How many issues can you actually export at once?
More than a decade of “why did my export stop at 1,000?” threads later, Atlassian finally moved the ceiling — but only on one of the two export paths.
| Export path | Limit | Where |
|---|---|---|
Older per-URL batch export (tempMax param) | 1,000 issues | Cloud (deprecated March 2026) + Server/Data Center |
| Newer asynchronous “Export CSV” from the Issue Navigator | 10,000 issues | Jira Cloud only, raised from 1,000 on March 19, 2025 |
REST API pagination (startAt / maxResults) | 1,000 per page, unlimited via looping | Cloud + Server/Data Center |
The 10,000-item raise applies specifically to that asynchronous export button in Jira Cloud’s Issue Navigator — not the classic export links, and not the REST API. If you’re still hitting a 1,000-issue wall in Cloud, you’re very likely on the older, now-deprecated export path rather than the current one. Server and Data Center customers don’t get the 10,000 bump at all: the default there is still 1,000, controlled by the jira.search.views.max.limit property, and Atlassian’s own guidance notes it’s “an intentional limitation within Jira to avoid performance-related issues such as an OutOfMemoryException” — a self-imposed ceiling, not a technical wall you can’t move as an admin (Atlassian Support).
The truncation trap — and how to avoid it
The dangerous part isn’t the limit itself, it’s that Jira doesn’t make it obvious when you’ve hit it. A long-open Atlassian ticket, filed in 2017 and still unresolved with 15 votes, describes exactly this: a search that returns more issues than the max limit doesn’t tell you how many you’re missing or how to fix it. Separately, Atlassian’s own KB on the 1,000-issue cap documents the limit and its workarounds without describing any on-screen alert when your filter’s real result count is bigger than what actually exported. In practice, the file downloads, opens cleanly, and just stops — so a spreadsheet that looks complete may quietly be missing however many issues sat past the cutoff. The only reliable check is comparing your filter’s total issue count (shown in the Issue Navigator) against the row count in the file you got.
Three ways to avoid getting burned by it:
- Confirm you’re on the async export path, not the old batch link. In Jira Cloud, that’s the “Export” menu on the Issue Navigator (“Export CSV (all fields)” / “Export CSV (current fields)”), which runs in the background and supports up to 10,000 issues — not a URL you’ve bookmarked with
tempMax=1000baked in. - Split with JQL when you’re over the ceiling. Atlassian’s own recommended workaround for exports larger than 10,000 items is to break the query into batches under the limit — by project, status, or a date range on
created,updated, orresolved— export each batch, then merge the files in Excel or Power Query. Always check your filter’s total count first so you know how many batches you actually need. - For a recurring pull, skip the manual batching. If this is a weekly or monthly ritual rather than a one-off, a marketplace app that’s built for bulk export removes both the row ceiling and the CSV-formatting problem in the same step (see below).
If you need a real spreadsheet, not just a bigger CSV
CSV solves the row-count problem eventually, through batching — it never solves the formatting problem, because CSV has no concept of formatting. If what you actually need is a genuine .xlsx file with formulas, multiple sheets, or scheduled delivery, that’s a marketplace app, not a native Jira feature. Three that are built specifically for this, plainly named:
- Better Excel Exporter for Jira (Midori) — exports real
.xlsxfiles with native formatting, formulas, and pivot tables, using configurable templates for issue lists, worklogs, or change history. - Exporter for Jira — built around PMO-style reporting, with a free tier that exports up to 20,000 issues in one run, past the native 1,000-row Jira limit, plus scheduled reports.
- Better Excel Automation for Jira (free, companion to Better Excel Exporter) — generates and emails Excel reports on a cron schedule or on issue events, so the spreadsheet lands in an inbox without anyone clicking export.
Crosstown Tech doesn’t build in this niche, so there’s no product pitch here — those three are simply the real options if native export isn’t enough.
One more thing worth separating out: if the actual goal isn’t a literal spreadsheet but getting Jira status in front of someone who doesn’t log into Jira, an export — CSV, Excel, or otherwise — is a snapshot that’s stale the moment you send it. That’s a different problem with a different answer; see Jira Reports for Stakeholders Who Don’t Use Jira and Export Jira Issues to OneNote for that version of the ask.