Someone edited a comment on a work item and the thread no longer makes sense. Or a comment you remember reading has gone entirely. You need to know what it said, who changed it, and when.
This comes up constantly in regulated teams, in support escalations, and in any project where a decision was recorded in a comment rather than a document. Here is what Jira gives you natively, where it stops, and what to do about the gap.
What Jira tracks natively
Jira does record that comments change. Open a work item and look at the Activity section, which has separate Comments and History tabs.
The Comments tab shows the current text of every comment. If a comment has been edited, Jira marks it as edited and shows the timestamp of the most recent change.
The History tab records field changes on the work item: status transitions, assignee changes, priority changes and so on.
For many teams this is enough. If you only need to know that something changed and roughly when, it is already there.
Where it stops
Three gaps catch people out, and they tend to be discovered at the worst possible moment.
1. Jira keeps only the most recent version of an edited comment. If a comment has been edited three times, you can see that it was edited and when the last edit happened. You cannot see what it said before. There is no way to compare versions.
2. Deleted comments are gone. When a comment is deleted, the content goes with it. Jira does not retain the text.
3. There is no per-work-item view of the comment trail. Even where change information exists, it is spread across tabs rather than presented as one chronological record of how a conversation evolved.
If you are trying to answer "what did this comment say before it was changed" or "what was in the comment that was deleted last Tuesday", native Jira will not tell you.
What to do about it
Option 1: prevent the problem with permissions
If the issue is that too many people can edit or delete comments, tighten the permission scheme first. This costs nothing.
In your project's permission scheme, look at:
- Edit All Comments and Delete All Comments. These let a user change or remove anyone's comment. In a lot of schemes these are granted far more widely than anyone intended. Restrict them to a small administrator group.
- Edit Own Comments and Delete Own Comments. More reasonable to grant broadly, but they still mean the author can quietly rewrite what they said.
This does not recover anything already lost, and it does not help when the edit was legitimate but you still need the earlier version. It does reduce how often the question comes up.
Option 2: export comments before they change
If you need a point-in-time record for a specific work item, you can pull comments through the REST API and store them yourself:
GET /rest/api/3/issue/{issueIdOrKey}/comment
This works, and it is free. The catch is that it only captures what exists at the moment you run it. It is a snapshot, not a history, so it only helps if you knew in advance that you would need it.
Option 3: keep a full version history automatically
If you need every previous version retained without anyone remembering to do anything, this is where an app makes sense.
Full disclosure: I work for Redmoon Software, and Comment History for Jira is our app. I have tried to make the sections above genuinely useful whether or not you use it.
Comment History for Jira captures every edit and every deletion automatically from the moment it is installed. Specifically:
- Every previous version is retained, with the author's name and the timestamp for each one, not just the latest edit.
- Deleted comments are kept, including their content. In Cloud they appear in the history with a red "deleted" marker, and prior versions of that comment are still listed in full.
- Each work item gets a Comment History tab in the Activity section, listing every current comment with its full edit and deletion history, grouped chronologically so a thread reads as a single timeline.
- Two filters keep long threads readable: Only Show Edited Comments hides comments that have no history, and Hide Comment History collapses the history so you see current comments only, with click-to-expand.
Practical details worth knowing before you evaluate it:
- It works on Cloud and Data Center.
- All data stays inside your Jira instance. Nothing is stored on Redmoon servers, which is usually the first question a security reviewer asks.
- No setup beyond installation. The tab appears on every work item immediately, and no re-index is required on Data Center.
- On Data Center you can also click the clock-with-arrow icon next to any individual comment to see a popup of that comment's versions. On Cloud there is a sidebar, opened with "View comment history", that shows the same information beside the work item so you do not lose your place.
There is a free trial on the Marketplace if you want to test it against a real project.
Which option fits
Situation | What to do |
|---|
Comments are being changed by too many people | Tighten Edit All and Delete All permissions |
You need a one-off record of a specific work item | Export via the REST API |
You need every version kept, including deletions | Use an app that retains history automatically |
You only need to know that something changed | Native Jira already does this |
Most teams should do the permissions review regardless. It is free, it takes ten minutes, and the default schemes are usually more permissive than people expect.
If you have run into this and solved it a different way, I would like to hear it. There are approaches I have not covered here, particularly for teams doing their own auditing through the API.
