Jira Comment Export: How to Track and Export Comment History in Jira
A significant amount of actual work occurs in Jira comments.
It is the place where teams justify decisions, confirm approvals, record blockers, and add technical details. Comments are included in the operational record of many teams.
The difficulty begins as someone poses a simple question: Can we export all of this? The question is typically posed by a project manager preparing a report, an auditor reviewing evidence, a compliance lead reviewing activity, or an IT team constructing a post-incident report.
Jira provides work-item-level history visibility, but teams frequently require something more extensive, searchable, and exportable for actual reporting processes.
So, let’s find out how to track and export full Jira comment history and what options are available.
Native options for tracking Jira comment edit history
Comment activity is partially visible in Jira, with critical limitations that may surprise users. Some events can be displayed in the History tab of each work item, including when a comment was removed, but it doesn’t show the actual text of the comment or the history of how the comment was changed over time. This implies that you can’t trust the History tab as a complete audit trail of comment activity.
Meanwhile, the Comments section within the work item shows when a comment has been added and edited (e.g., with an edited label). Nonetheless, it only shows the most recent version of the comment and doesn’t indicate previous versions or changes over time. That is, you can view that a comment has been edited, but not what was changed.
A frequently asked question in the Atlassian Community is whether JQL can be used to track the Jira comment history of multiple work items. Unfortunately, this isn’t possible. JQL can return the number of comments, but doesn’t provide access to comment content, edit history, or change tracking.
Native options for Jira export comments
Jira offers a few native options for exporting comment-related data, but they come with significant limitations.
First, you can export the history of an individual work item using Jira’s built-in export functionality. You can export work item comments, for example, to Excel. It will look like this:
However, this approach is limited to a single work item at a time and doesn’t provide a complete history of comment changes. It is not possible to check which comments were edited and which were deleted.
Another common workaround for exporting Jira comment history of multiple work items is to use JQL. First, filter the work items, then go to More actions → Export → CSV (All fields). After exporting, you can convert the CSV file into an Excel spreadsheet to make it more readable and easier to work with. You will receive such a result:
While this method includes comment data, it has several important drawbacks:
- The structure isn’t optimized for comment analysis
- It is difficult to clearly see who added each comment
- There is no visibility into the edits of comments
- Deleted comments are not tracked at all
Although this workaround can provide access to comment changes, it isn’t suitable for audits, compliance checks, or detailed investigations, which require a full and reliable Jira comment history.
Jira Comment Tracking and Export Using Issue History for Jira App
To overcome Jira’s native limitations, Issue History for Jira (Work Item History) app provides a much more detailed and audit-friendly way to track comment additions and updates.
Track Jira comment history at the work item level
After the app installation, Issue History Panel View will be available within every work item. It lets you focus on the comment field with the Field filter.
After the activation of the “Tracking comment changes” feature, you can easily see:
- when a comment was added, edited, or deleted
- who did the action
- changes that have been made (both old and new values)
Unlike native Jira functionality, this provides you with full insight into how comments have changed over time. You no longer have to view the latest version only, but can follow the entire comment lifecycle in an organized, chronological way.
You also have the option to export the detailed Jira work item comment history in Excel, CSV, or PDF formats.
The comment history export in Excel format will look like this:
Track and export comment history across multiple work items
For broader analysis, Issue History for Jira (Work Item History) app provides a Table View designed for reporting across multiple work items.
In this view, you can:
- Apply filters such as project (space), date range, users, and other fields
- Customize your report using the Columns option to include relevant fields
- Focus specifically on comment-related changes within a larger dataset
Once your report is ready, you can export it to Excel or CSV in just a few clicks.
The example of a report in Excel format:
The result is a clean, structured, and readable file that includes detailed comment history across multiple work items. This makes it highly valuable for:
- audits and compliance checks
- incident investigations
- project reviews and reporting
With this approach, Jira comment tracking becomes not only possible but also scalable, transparent, and ready for real-world business needs.
Summing Up
The built-in features of Jira allow you to view and export certain comment-related data. However, they don’t provide complete visibility or audit-ready reporting. When you look at a single work item or multiple work items, the absence of detailed comment history and formatted exports makes investigations and compliance processes significantly more difficult.
By using the Issue History for Jira (Work Item History) app, you have full access to comment history and the ability to export clean, structured reports for audits, incident investigations, and project reviews.
| Need full visibility into Jira comment history?
Track every comment change, see who edited what and when, and export detailed reports for audits, compliance, and investigations. 👉 Try Issue History for Jira (Work Item History) on Atlassian Marketplace |
Was this helpful?
Thanks!
Natalia_Kovalchuk_SaaSJet_
2 comments