nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

I need the data exported in excel for tickets

Mohit Verma

Hi Team,

I am looking for an efficient way to export the data from JIRA service management to excel for internal audit and clean up activities.

Is there a possibility to take the dump of tickets from JIRA to excel which includes Ticket number, Description, criticality, urgency, assignee, reporter, customer, Internal Comments, External Comments, Work logged details on the same sheet in different columns.

It be helpful if this can be done in an automated format as we are looking for year by year data.

Thanks.

Mohit

Accepted answers

All comments

Matthew Sinclair

You will need access to the Space (Browse permission) and possibly a bit more.

After that you can do a JQL/Filter for what you want and do an export - however you are limited to 10k tickets at a time. ( I think?? )

This will help get you started:

https://community.atlassian.com/forums/discussion/2814825/jira-export-6-tips-to-jira-export-to-excel-csv-pdf-and-more

Arkadiusz Wroblewski

Hello @Mohit Verma

Do you need a one-time export or a scheduled report?

Cheers

Arek🤠🧙‍♂️

Artyom Karpets _ArtUp Labs_

Hi Mohit,

To add to Matthew's answer, here is what the built-in export gives you for this list and where it stops.

Built-in: Export CSV (all fields) from the work item search. Use one JQL per year, for example project = HELP AND created >= 2025-01-01 AND created < 2026-01-01.

Key, Description, Assignee, Reporter, Organizations and your criticality and urgency fields (Priority, Impact, Urgency or custom fields) come out as columns.
Each comment goes into its own "Comment" column in chronological order, with date, author and text. The CSV does not say whether a comment was internal or shared with the customer.
Work logs come out as "Log Work" columns in the same way.
The asynchronous CSV export takes up to 10,000 work items per run, so one year usually fits. Above that, see Atlassian's KB "Export over 10,000 work items in Jira Cloud".

Internal vs. external comments: the JSM REST API can split them. GET /rest/servicedeskapi/request/{issueIdOrKey}/comment?public=false returns only internal comments, ?internal=false only public ones. The platform API (/rest/api/3/issue/{key}/comment) also returns a jsdPublic flag on each comment.

Automated, year by year: Jira has no built-in scheduled export to Excel. The usual route is a small script against the REST API (JQL search, then comments and work logs per work item) run on a schedule, or a Marketplace app.

Disclosure: I'm the developer of ArtUp Reports. It exports a JQL result to a real .xlsx with comments and work logs as columns, either one row per work item or one row per comment / per work log, which is easier to audit than dozens of "Comment" columns. It does not mark comments as internal or public and does not schedule exports, so for those two points the API route above is the one that works: ArtUp Reports on the Marketplace

Written with help from an AI assistant.

Paul Glantschnig _Appfire_

Hi @Mohit Verma,

The built-in CSV export with one JQL per year is a solid baseline. The two pain points for an audit are usually the comments (spread over many "Comment" columns, with no internal/external marker) and having to rebuild the column set each time.

If you're open to an app from the Atlassian Marketplace, JXL for Jira covers most of your list in a single sheet that you can export to XLSX:

Standard fields: Key, Description, Priority, Assignee, Reporter, Organizations, Request participants, plus your criticality/urgency fields (system or custom).
Comments: smart columns such as All comments and All external comments put every comment of that kind into one cell, so external comments get their own column. There are also first/last internal comment columns, but no single "all internal comments" column today.
Work logs: Time spent and Σ Time spent are available as totals. Individual work log entries (who, when, how much) are not broken out per row, so for line-by-line work log detail the REST API route is still the better fit.
Year by year: set the sheet scope to a JQL like project = HELP AND created >= 2025-01-01 AND created < 2026-01-01, or copy the sheet once per year and adjust the dates. The column setup stays saved, so each export is a few clicks via More > Export > XLSX.

To be transparent, JXL has no scheduled export, so the export itself is still a manual click.

All comments smart column in a JXL sheet

Disclosure: I work for the team that builds JXL.

Hope that helps,
Paul

Danut M _StonikByte_

Hi @Mohit Verma,

As previously mentioned, you can export issues from the search screen using Export > Excel CSV. This allows you to export either the selected fields or all fields for the issues returned by the filter, including comments. However, as far as I can see, worklogs cannot be exported using this method.

But why struggle with complicated and time-consuming data exports when you can audit and analyze your data directly in Jira, without exporting anything? You could simply use an Excel-like reporting tool that runs within Jira, available on the Atlassian Marketplace.

If you're open to using an app from the Atlassian Marketplace, I would recommend checking out the Pivot Table & Pivot Chart and Worklog Reports & Timesheets gadgets, both included in our Great Gadgets add-on for Jira & Confluence.

With these gadgets, you can easily create a wide variety of pivot tables, pivot charts, timesheets, and custom reports, just like in Excel, but with the added benefit of working directly with your Jira data, without the hassle of exporting and manually processing it.

Hope this helps. If you need a demo or more details, please contact our support at any time.

Danut.

Birkan Yildiz _OBSS_

Hey @Mohit Verma,

Exporting JSM tickets along with custom fields, comments, and worklog details for internal audits is a very common requirement, but it comes with a few native caveats in Jira.

If you need an out-of-the-box audit report that neatly structures field values, comments, and changes into exportable Excel columns, you can use Historian - Issue History for Jira:

Field-Level Selection: With History Explore report, you can customize your report by selecting only the specific standard and custom fields you need (Ticket Key, Description, Criticality, Urgency, Assignee, Reporter, Comments, etc.) so they display side-by-side as clean columns.

Audit-Ready Excel Export: Export the complete, structured report directly to XLSX or CSV for offline archiving, audit compliance, and cleanup.

Year-by-Year Audit Snapshots (Historic Query): You can also use the Historic Query feature to run a JQL search and view the exact state of your JSM backlog as it appeared at the end of any specific year (e.g., Dec 31st), replacing manual tracking with objective audit snapshots.

You can find Historian - Issue History for Jira on the Atlassian Marketplace.

Disclosure: I am part of the OBSS team, the creators of Historian.

Best,
Birkan

Tomasz Kustrzynski ~Advanced Insights~

Hi @Mohit Verma,

Since you want it year by year on a schedule: Jira can't send a recurring Excel export by itself, so it's either a script against the REST API on a timer or an app.

I work on Advanced Export, so I'm biased, but this is what it was actually built for.

In short - you can set up scheduled report which sends/uploads to SFTP a file (XLSX or CSV) with report. The secret sauce here is SQL processing, so that your report can contain exactly the columns you require.

Here's what setup for your report could look like:

you specify JQL to define what work items get exported
fields extracted from work items - key, log work, comment (and others as needed)
SQL which runs on the dataset built from the JQL and fields

Example results

Key	Internal comments	External comments	Work logged	Total hours
HELP-1	Checked the logs	Thanks, looking into it⏎Fixed, please confirm	Alex Morgan, 2025-03-02, 1.5h: Investigation⏎Sam Lee, 2025-03-03, 0.5h	2
HELP-2			Alex Morgan, 2025-04-01, 1.0h: Call with customer	1
HELP-3	Cannot reproduce

I wrote an article covering your exact case with more detailed description of the setup: https://docs.advancedinsights.app/atlassian/advanced-export/sql-exports/comments-and-worklogs

Advanced Export has its own Rovo agent, so if you use Rovo, your report can be 1 prompt away from being scheduled and delivered.

Hope that helps!