Hi everyone. I'm Artyom, and I build ArtUp Reports, a Marketplace app that exports Jira issues to files. "How do I get this filter into Excel" and "how do I make a Word report from Jira" come up here often, so here is what Jira Cloud already does, where it stops, and how we handle the rest.
What Jira Cloud does natively
CSV from the issue search. In the list view of a search, use Export → Export CSV (current fields) or (all fields). According to Atlassian's KB "Export over 10,000 work items in Jira Cloud", the asynchronous CSV export handles up to 10,000 work items; a progress bar appears in the bottom-left corner while it runs.
A few tips:
- Prefer current fields. The KB notes that the all-fields export is slow and produces large files. Set the columns in the list view first.
- Open the file in Excel through Data → From Text/CSV instead of double-clicking it. You choose UTF-8 and the delimiter yourself, so non-Latin text, dates and numbers come through correctly.
- More than 10,000 issues: split the JQL, for example by
created date ranges, and export in parts.
Jira Cloud for Sheets. Atlassian's own Google Sheets add-on pulls the result of a JQL query into a sheet. It suits a working table better than a one-off file.
Where native export stops
- CSV is plain text: no data types, no formatting, issue keys are not links.
- There is no Word or PDF document built from your own layout. A status report, release notes or a document for a customer gets assembled by hand.
- CSV carries attachment links, not the images themselves.
How ArtUp Reports handles it
Disclosure: this is my app. It opens from Apps → Export to Excel, Word or PDF on the issue search, from a board, backlog or sprint, and from a single issue.
- Excel. A real .xlsx: dates are dates, numbers are numbers, issue keys link to the issues. Frozen header and filters, one row per issue, work log or comment, and an optional Summary sheet with counts by status, assignee and priority. In our test on a seeded site, 10,003 issues went to Excel in 11.8 seconds (the app's export pipeline run outside the browser; your time depends on the site and network).
- Word templates without code. Write placeholders such as
{{summary}} in an ordinary .docx made in Word, and the app fills it, with images and tables. Mistyped placeholders are caught when you upload the template. Built-in layouts: single issue, issue list, sprint report, release notes. - PDF. The same four layouts on A4 or Letter, images embedded, fonts for Latin, Cyrillic and CJK bundled.
- Data stays in Atlassian. It is a Forge app: the file is built in your browser with your Jira permissions, there are no external servers, and issue content is not stored.
What it does not do: it does not import a spreadsheet back into Jira, does not schedule or email exports, and works with Jira Cloud only.
Marketplace listing: ArtUp Reports – Excel, Word & PDF export for Jira
If you export from Jira regularly, which report do you still end up fixing by hand? I'm collecting cases for the next built-in templates.
Written with help from an AI assistant.
