# Export Jira issues to Excel or CSV

Reporting, stakeholders, and audits need your Jira data somewhere Jira is not. Learn how to export issues to Excel and CSV without timeouts.

> Learn how to export Jira issues to Excel and CSV with custom field selection and JQL — even large result sets the native export times out on.

## Why this matters in Jira

Jira is built for tracking work, not for reporting on it. The moment someone needs a spreadsheet — a stakeholder pack, an audit, a budget review, a migration mapping — the data has to leave Jira, and the native export is not built for that. It times out on large result sets, dumps whatever fields it decides, and produces files that need an hour of cleanup before they are usable. The result is that reporting becomes a manual, error-prone chore that nobody wants to own.

### Reporting happens outside Jira

Finance, leadership, and clients want a file they can open, not a Jira filter they have to learn. The audit team wants a CSV for evidence. The migration team wants a mapping spreadsheet. Exporting exactly the fields they need, in the right format and column order, is the difference between a one-click job and a one-hour manual reformatting session every single week.

### Native export times out at scale

Jira’s built-in CSV export is designed for small result sets. Once you go past roughly a thousand issues — common for any real project, quarterly review, or compliance pull — it times out, truncates, or fails silently. Teams with actual data fall back to exporting in batches and stitching files together by hand, which is slow and quietly lossy.

### Field control matters

The native export includes whatever columns Jira’s issue navigator happens to show, which is rarely what the report needs. Custom fields end up with unreadable IDs, dates land in inconsistent formats, and the column order never matches what the receiving spreadsheet or system expects. Reliable reporting means choosing the exact fields and their order, driven by a saved JQL filter so the output is identical every time.

### Custom fields and encoding break imports

Jira issues are full of special characters — code snippets, non-ASCII names, commas inside descriptions. If the export does not handle UTF-8 encoding and proper CSV quoting, those characters arrive corrupted or shift every column on import. Most teams discover this only when a stakeholder opens a broken file.

### Repeatability beats one-off exports

A report that has to be regenerated weekly or monthly should not be rebuilt from scratch each time. When the export is driven by a saved JQL filter and a fixed field selection, rerunning it is one click and the output is consistent. That is what makes reporting sustainable instead of a recurring fire drill.

## The approach that works

A repeatable export workflow has four moving parts: define the dataset with JQL, choose the exact fields and their order, pick the right output format, and run the export with a tool that handles scale. Get those right once and every subsequent report is a one-click rerun.

1. **Define the dataset with JQL.** Write a JQL filter that captures exactly the issues you want — by project, status, date range, assignee, or any combination of standard and custom fields. Save the filter so you can rerun the same export next week without rebuilding the query. A good filter is the difference between a clean dataset and one full of edge-case issues that skew the report.

2. **Choose the fields and column order.** Select exactly which fields appear in the export and in what order. Include the issue key, summary, status, and dates by default, then add the custom fields the report actually needs. Match the column order to what the receiving spreadsheet or downstream system expects, so no manual rearranging is required after export.

3. **Pick the right output format.** Choose XLS or XLSX when the recipient will open the file in Excel and expects formatting, multiple sheets, or native number handling. Choose CSV when the file is destined for another system, a database import, or a script. The right format up front avoids conversion steps later.

4. **Export without timeouts.** Run the export with a tool that streams large result sets instead of loading them all into memory. This is what lets thousands of issues come down reliably in one file — the native export fails precisely because it tries to build the whole file at once and hits a server limit.

5. **Handle encoding and special characters.** Make sure the export produces UTF-8 encoded files with proper CSV quoting, so commas, line breaks, and non-ASCII characters in descriptions and comments survive the round trip intact. Spot-check a few rows after export, especially any field known to contain code or pasted text.

6. **Save and rerun on a schedule.** Once the JQL filter and field selection are right, save them. Rerun the same export each week, month, or quarter to produce a consistent, up-to-date dataset for the recurring report. The goal is to turn reporting from a project into a button.

## This solution is for you if…

- Project managers and team leads producing weekly or monthly stakeholder reports

- Finance, audit, and compliance teams pulling evidence out of Jira

- Engineering leads exporting backlogs or sprint data for planning and retrospectives

- Migration teams building mapping spreadsheets to move data between systems

- Anyone who needs large Jira exports the native CSV tool cannot handle

## Our apps that solve this

- **[Simple Bulk Issues Excel CSV Export for Jira](/apps/simple-bulk-issues-excel-csv-export-for-jira.md)** — Export filtered Jira issues to Excel/CSV with customizable field selection · [Install from Atlassian Marketplace](https://marketplace.atlassian.com/apps/3818473739/simple-bulk-issues-excel-csv-export-for-jira?utm_source=ngpilot.com&utm_medium=website&utm_campaign=scenario-export-jira-issues-to-excel)

## Read the guides

- [Export Jira Issues to Excel or CSV: Complete Guide (2026)](/blog/export-jira-issues-to-excel.md)

- [How to Export Jira Issues to Excel for Stakeholder Reporting](/blog/export-jira-issues-to-excel-csv-reporting.md)

- [Export Jira Audit Logs for Compliance Reviews](/blog/export-jira-audit-logs-compliance.md)

- [Export Jira Issues to CSV/Excel: Common Problems & FAQ](/blog/faq-exporting-jira-issues.md)

- [Jira Bulk Operations FAQ: Exports, Edits & Downloads](/blog/faq-bulk-operations-jira.md)

## Frequently asked questions

### How do I export more than 1,000 Jira issues to Excel?

Jira’s native CSV export times out on large result sets — typically above roughly a thousand issues. A bulk export app streams the result set instead of loading it all at once, so thousands of issues export reliably in one file, with custom field selection and a JQL-driven filter, outputting XLS, XLSX, or CSV.

### Can I choose which fields to export from Jira?

Yes. A purpose-built export tool lets you select exactly which standard and custom fields to include and in what column order, so the file matches what your reporting tool or downstream system expects — no manual rearranging after export.

### Can I repeat the same export each week?

Yes. Drive the export from a saved JQL filter and a fixed field selection, then rerun it any time. The output is consistent across runs, which turns a recurring report from a rebuild into a one-click refresh.

### Why do special characters break in my Jira CSV export?

CSV files must be UTF-8 encoded and properly quote any field containing commas, line breaks, or double quotes. If the export tool does not handle this, descriptions and comments with special characters arrive corrupted or shift every column on import. A reliable export tool generates UTF-8 files with correct quoting by default.

### Should I export to Excel (XLSX) or CSV?

Export to XLSX when the recipient will open the file in Excel and expects native formatting or multiple sheets. Export to CSV when the file is destined for another system, a database import, or a script. CSV is smaller and more portable; XLSX is friendlier for humans.

### Can I export Jira custom fields?

Yes. Custom fields can be included in the export just like standard fields. Choose the ones the report needs by their display name, and they will appear as readable columns rather than raw custom-field IDs.

## Ready to try it?

All NGPILOT apps are free for up to 10 users and install in one click from the Atlassian Marketplace. Browse the [full app catalog](/apps.md) or read more [scenario solutions](/solutions.md).