# Jira Export Limit: How to Export More Than 1,000 Issues (2026) September 2, 2026 · 5 min read [NGPilot](https://ngpilot.com) Quick Answer Jira Cloud's native export stops at 1,000 issues per export and only includes columns visible in the issue navigator. To export more: split your filter into JQL batches, use the REST API, or install [Simple Bulk Issues Excel CSV Export](https://marketplace.atlassian.com/apps/3818473739/simple-bulk-issues-excel-csv-export-for-jira?utm_source=ngpilot.com\&utm_medium=blog), which exports up to 5,000 issues per run in CSV, XLS, or XLSX — and tells you plainly when a result set was truncated. If you have ever exported a project for reporting, an audit, or a migration, you have probably run into Jira Cloud's export limit without being warned first: the export finishes, the file looks complete, and the row count quietly stops at 1,000. This article explains where that limit comes from, then compares the three practical ways to export larger issue sets in 2026. ## Why native Jira exports stop at 1,000 issues[​](#why-native-jira-exports-stop-at-1000-issues "Direct link to Why native Jira exports stop at 1,000 issues") Jira Cloud's issue navigator export is designed for quick, ad-hoc handoffs, not bulk data extraction. Atlassian documents the constraint: a native export includes at most 1,000 issues, and only the fields currently shown as columns in your navigator. Two consequences follow from how it is built: 1. **Column selection is indirect.** You have to add each field you want as a navigator column first — including every custom field. 2. **The cap is silent.** The exported file gives no indication that rows beyond 1,000 exist, so a truncated export looks exactly like a complete one. None of this is a bug — it is a scope decision. But for reporting, backup, or migration work, 1,000 rows is often a fraction of the real result set. ## Three ways to export more than 1,000 issues[​](#three-ways-to-export-more-than-1000-issues "Direct link to Three ways to export more than 1,000 issues") | Approach | Max issues | Formats | Custom fields | Effort | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | -------------- | --------------------- | ------------------ | | Native export + JQL splitting | 1,000 per batch | CSV | Add columns manually | Manual, repetitive | | [Simple Bulk Issues Excel CSV Export](https://marketplace.atlassian.com/apps/3818473739/simple-bulk-issues-excel-csv-export-for-jira?utm_source=ngpilot.com\&utm_medium=blog) | 5,000 per export | CSV, XLS, XLSX | Pick from a checklist | One-time setup | | Jira REST API (paginated search) | Effectively unbounded | JSON | Explicit field lists | Scripting required | ### Option 1: Split the export with JQL[​](#option-1-split-the-export-with-jql "Direct link to Option 1: Split the export with JQL") The zero-cost approach: divide a big result set into batches that each stay under 1,000 issues, then merge the files yourself. ``` project = ENG AND updated >= -30d project = ENG AND updated < -30d AND updated >= -60d ``` Works, but each batch means re-adding columns, re-exporting, and stitching CSVs together — and nothing tells you whether a batch itself overflowed. ### Option 2: A Marketplace export app[​](#option-2-a-marketplace-export-app "Direct link to Option 2: A Marketplace export app") [Simple Bulk Issues Excel CSV Export](https://marketplace.atlassian.com/apps/3818473739/simple-bulk-issues-excel-csv-export-for-jira?utm_source=ngpilot.com\&utm_medium=blog) runs from the issue navigator on whatever JQL you already have, and as of the September 2026 release: * **Exports up to 5,000 issues per run** (previously 1,000) * **Truncation is never silent** — if a filter matches more than 5,000 issues, the result message tells you exactly how many rows you got and suggests narrowing the filter * **Field selection is a checklist** — system fields, custom fields, and now the **Parent field**, exported as the parent issue key (for example `PROJ-123`) for subtask and hierarchy reporting * **CSV, XLS, and XLSX output** in a single download, with UTF-8 encoding handled correctly The full walkthrough — including JQL examples and field-selection tips — is in our [Jira to Excel export guide](/blog/export-jira-issues-to-excel.md). ### Option 3: The REST API[​](#option-3-the-rest-api "Direct link to Option 3: The REST API") For recurring, fully automated pipelines, the [enhanced search REST endpoint](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-search/) paginates arbitrarily large result sets with `nextPageToken`. It serves up to 5,000 issues per page, and it is the same endpoint Simple Bulk Issues uses under the hood. Choose this when exports need to run unattended; choose the app when a human needs a file now. ## What if your result set is bigger than 5,000?[​](#what-if-your-result-set-is-bigger-than-5000 "Direct link to What if your result set is bigger than 5,000?") No single export tool removes the ceiling entirely — at some point, splitting is the right answer. The difference is knowing where the edge is: * **Native export:** cuts at 1,000 rows without telling you * **Simple Bulk Issues:** cuts at 5,000 rows and tells you it did * **REST API:** no practical ceiling, but you own the scripting A filter that matches 12,000 issues exports cleanly as three batches — for example `created <= 2025-12-31`, the following six months, and `created > 2026-06-30`. ## Frequently Asked Questions[​](#frequently-asked-questions "Direct link to Frequently Asked Questions") ### What is the export limit in Jira Cloud?[​](#what-is-the-export-limit-in-jira-cloud "Direct link to What is the export limit in Jira Cloud?") Jira Cloud's native export from the issue navigator caps at 1,000 issues per export, and only includes the columns currently visible in your navigator. There is no native XLSX option — just CSV with all fields or CSV with current fields. ### How do I export more than 1,000 issues from Jira?[​](#how-do-i-export-more-than-1000-issues-from-jira "Direct link to How do I export more than 1,000 issues from Jira?") Three options: split the filter into JQL date or project ranges and export in batches; use a Marketplace app like Simple Bulk Issues Excel CSV Export (up to 5,000 issues per run in CSV, XLS, or XLSX); or script the paginated REST API for automated pipelines. ### How many issues can Simple Bulk Issues Export handle?[​](#how-many-issues-can-simple-bulk-issues-export-handle "Direct link to How many issues can Simple Bulk Issues Export handle?") Up to 5,000 issues per export as of September 2026 (raised from 1,000). If a filter matches more than 5,000, the app says so in the result message instead of silently cutting rows. ### Does the export include the Parent field?[​](#does-the-export-include-the-parent-field "Direct link to Does the export include the Parent field?") Yes. Simple Bulk Issues exports the Parent field as the parent issue key (for example PROJ-123), which keeps subtask and parent-child hierarchies intact in the exported file. *** More export troubleshooting — encoding, field mismatches, timeouts — is covered in our [Jira export FAQ](/blog/faq-exporting-jira-issues.md). ## Related guides * [How to Create Mermaid Diagrams in Jira](/blog/how-to-create-mermaid-diagrams-jira.md) * [Export Jira Issues to Excel or CSV](/blog/export-jira-issues-to-excel.md) * [Bulk Download Jira Attachments](/blog/bulk-download-jira-attachments.md) * [How to Migrate Confluence Content](/blog/how-to-migrate-confluence-content.md) * [How to Add a Block Quote in Confluence](/blog/block-quote-confluence.md) Explore NGPILOT[Browse Solutions](/solutions.md)[All Apps](/apps.md)[Atlassian Marketplace →](https://marketplace.atlassian.com/vendors/1226848/?utm_source=ngpilot.com\&utm_medium=blog\&utm_campaign=hub-links) **Tags:** * [jira](/blog/tags/jira.md) * [export](/blog/tags/export.md) * [excel](/blog/tags/excel.md) * [csv](/blog/tags/csv.md) * [jira-cloud](/blog/tags/jira-cloud.md) * [reporting](/blog/tags/reporting.md)