Export Jira Issues to Excel with a JQL Filter

Why Jira's built-in export isn't enough

Jira Cloud's issue navigator has an "Export" menu with CSV options, but the output is a flat text file: no column types, no styling, and no reliable behaviour once a result set runs into the thousands. Large JQL results either time out in the browser or export as a single unformatted sheet that still needs cleanup before anyone can use it for reporting or a bulk edit. There's also no built-in way to page through a big result and keep exporting until it's complete — you get one pass, and if it fails partway you start over.

What a real JQL-to-Excel export needs

• Paging through the full result set, not just the first page the API returns by default.
• A genuine .xlsx workbook with typed columns (dates as dates, numbers as numbers), not a CSV that Excel has to guess at.
• Column styling and header formatting that survives being reopened, sorted, and filtered.
• A result that round-trips: the same file structure can be edited and fed back in for an import, not just read once and thrown away.

Saved filters vs. one-off JQL

A saved filter is just a stored JQL string — exporting from a saved filter and exporting from a JQL query typed fresh produce the same result, so there's no need to save a filter first if the query is a one-off. For anything reused weekly (a sprint report, a stakeholder export), saving the filter means the same export can be re-run without retyping the query, and the workbook stays consistent run to run.

Checking the export is complete

1. Run the JQL in Jira's own issue navigator first and note the total issue count.
2. Export the workbook and check its row count matches — an export that silently truncates at a page boundary is the most common way large exports go wrong.
3. Spot-check a handful of rows against the issue view directly, particularly custom fields and multi-value fields like labels or components.
4. Confirm dates exported as real Excel dates, not text strings, if the export will be sorted or filtered by date afterward.

Feeding the export back in

The round-trip only works if the reimport side handles the same file cleanly. Jira's own import tools only take CSV, not .xlsx, so getting an edited workbook back in usually means a conversion step first. See importing Jira issues from Excel for what that conversion changes and where Jira's native importer runs into limits.