The majority of teamwork occurs in Jira comments. Updates are shared, things are clarified, and decisions are made directly within the task. However, there are cases when comments are edited or even removed, and that can be confusing.
Suppose you read some critical comment yesterday, and now it is different or not there at all. Who changed it? What did it say before?
Tracking comment history in Jira is helpful for:
In this article, we will explore Jira's insights into comment edits and deletions, understand the limits, and demonstrate how to utilize the Issue History for Jira app to gain a comprehensive view.
Comments in Jira are not simply casual notes. They are an important part of decision-making related to the performance of any task. This is why the ability to monitor their edits and deletions can significantly benefit teams:
Put simply, in the absence of a clear history of comment changes, teams run the risk of misunderstanding, wasted knowledge, and non-compliance.
Jira provides limited visibility into the changes to comments by default. You may see that something has been edited, but the information is quite minimal, and there is no tracking of deletions.
Jira shows the comment that has been edited. The disadvantage is that Jira shows only the latest version of the comment. The whole history of editing cannot be accessed, nor can the previous version be compared.
Once a comment is deleted in Jira, it is gone forever.
With Jira native functionality, there is no visible record of what was deleted. Using the History tab in every Jira work item, you can only see that the comment was deleted and who was responsible. But you won’t know the details.
It may be a problem in teams where the comments are a component of their documentation or decision-making process.
💡 Practical Tip: Rather than deleting comments, invite your team to leave them there and write an additional explanatory comment below. The other alternative is to use formatting such as strikethrough to indicate that the old comment is no longer relevant, while still maintaining context.
Jira native tools don’t provide a complete view of comments edits, or deletions. This is why the Issue History in Jira app is used by many teams to get complete visibility.
With Issue History for Jira app, you can:
To get the comment history and export it, after Issue History app installation and the activation of the tracking comment changes functionality, you need to do the following:
If you just need to track comment changes related to one specific work item, you can use Panel View of Issue History for Jira app. There, you can choose the required date range and use a Field filter to see the changes related only to the Comment field. For example:
💬 Track comment edits and deletions in Jira Get a complete history of comment changes with Issue History for Jira. |
Jira provides only a partial view of the edits and deletions of comments, enough to see that something has changed, but not what and why. This may create gaps in teams where transparency, accountability, and compliance are important.
Issue History for Jira app fills those gaps with a complete, easy to read history of all comment changes, powerful filters, and export. It is the easiest method to have a complete reliable record of the changes happened to Jira work items.
Natalia_Kovalchuk_SaaSJet_
Product Marketer
SaaSJet
2 accepted answers
1 comment