In Jira Data Center, the "History" tab provides a clear, chronological log of changes to issue fields such as status, assignee, summary, and more. However, changes to comments—including deletions only—are not tracked in this unified history. Currently, comment edits are only indicated by an "edited" label within the comment itself, and there is no built-in way to view previous versions or see comment changes alongside other issue field changes.

Additionally the Deleted comments are part of change history however the format for API is not in sync with other Jira fields

For Comment:

items": [
                    {
                        "field": "Comment",
                        "fieldtype": "jira",
                        "from": "This is test comment\r\n\r\n ",
                        "fromString": null,
                        "to": null,
                        "toString": null
                    }
                ]
 

For other issue fields:

"items": [
                    {
                        "field": "resolution",
                        "fieldtype": "jira",
                        "from": "10000",
                        "fromString": "Done",
                        "to": null,
                        "toString": null
                    },
                    {
                        "field": "status",
                        "fieldtype": "jira",
                        "from": "10001",
                        "fromString": "Done",
                        "to": "3",
                        "toString": "In Progress"
                    }
                ]
 

This inconsistency creates challenges for teams that rely on Jira Data Center for compliance, auditing, and transparency, as comments often contain critical information, decisions, or context related to the issue.

Proposed Solution

• Track all comment changes (add, edit, delete) in the issue’s History tab, using the same format as other field changes.

• • Each comment change should log:

• • • The user who made the change

• • • The timestamp

• • • The action (added, edited, deleted)

• • • For edits, the previous and new versions of the comment (with privacy controls as needed)

• Ensure the format and structure of comment change entries match those of other field changes for consistency and ease of review.

• Optionally, provide a diff view for comment edits to highlight what was changed.