Haulcopy

Checked against Atlassian’s docs on 17 Oct 2026

Export Jira issues to Excel

Jira Cloud can already send a search to a spreadsheet. The file it calls Excel is usually a CSV, and one export stops at 10,000 issues. That is enough for a lot of reports. It is a poor fit when you need typed date cells, a file over that line, or the same workbook again next Monday.

What Jira’s own export does

From a work-item search, open the more-actions menu and choose Export. Atlassian’s export search results page lists CSV, Google Sheets, Word, Excel, XML, and form data. The Excel entries are named:

Those are CSV files with an Excel-oriented name, encoded as UTF-8. Older Excel builds sometimes read that UTF-8 as ANSI, so non-English text looks wrong until you import the file instead of double-clicking it. Atlassian also warns against uploading the CSV into Sheets or Excel because a crafted file can carry macros. The safer native path into a grid is the Open in Microsoft Excel or Open in Google Sheets icon above the search, which is a connector, not a file you keep.

There is a real .xlsx export, and it is narrow: Export XLSX (form data) writes Jira Service Management form responses, plus any Jira columns you had selected. Work items that do not have that form are left out. It is not a general issue-to-Excel export.

The 10,000-issue line

Until 19 March 2025 the navigator export was capped at 1,000 issues. Atlassian then raised the asynchronous CSV export to 10,000. The announcement is You Asked, We Delivered. The support article Export over 10,000 work items in Jira Cloud is the current ceiling: one async Export CSV from the issue navigator covers up to 10,000 work items.

All-fields exports are the slow ones. Atlassian tells you to avoid “all fields” when you can, because the file gets large and the job takes longer. The export runs in the background and pings you in Jira when the download is ready. You can leave the page.

That 10,000 cap is the navigator UI. It is not the REST API. API pagination was not raised with it.

Jira Cloud for Sheets

Jira Cloud for Sheets imports a JQL or a filter into Google Sheets. Atlassian says the add-on is fine up to 10,000 work items. Past that, use the =JIRA() function twice, with a start offset, and sort the JQL so the two pages do not drift:

=JIRA("project = PROJ order by key", "", 0, 10000)
=JIRA("project = PROJ order by key", "", 10000, 10000)

The sheet then lives in Google, which is a different system from the Jira site.

When the native file is the right tool

Use Jira’s export if the search is under 10,000, the columns on screen are the columns you want, and a CSV is acceptable. You do not need an app for that.

What Haulcopy adds, and what was actually run

Haulcopy writes a real .xlsx: date and number cells, a frozen header, an autofilter, column widths, and a hyperlink on the issue key. You pick up to 50 fields. Key is always the first column. The page shows progress. Over 10,000 issues, it writes separate files of 10,000 instead of asking you to slice the JQL.

On 16 Oct 2026 a 10,000-issue, 50-field Excel export completed on one developer site. That is one measured run, not a promise that every customer site will match its speed. Jira’s rate limits still apply. One export runs at a time on a site. The file stays in Jira and expires after seven days.

Price, once the Marketplace listing exists: free up to 10 Jira users, then $1.49 per user per month, billed by Atlassian. The listing is not up yet. Docs.