Issue Summary

Jira Cloud for Slack app sends a notification showing the wrong user as the actor when a comment is deleted.

Example Scenario

This is similar to https://jira.atlassian.com/browse/JRACLOUD-94799, where Slack notifications are attributed to the wrong user. However, in this case there are no shared accounts in use.
When a comment is deleted on a Jira issue, Jira itself correctly identifies the user who deleted the comment, but the Slack notification from the Jira Cloud app attributes the deletion to a different user (the original commenter).

Steps to Reproduce

1. Have User A create an issue
   • Email (example): userA@example.com
2. Have User B add a comment on that issue
   • Email (example): userB@example.com
3. Have User C delete the comment that User B added on that same issue
   • Email (example): userC@example.com
4. Observe notifications:

• • User B receives a Jira notification stating that User C deleted their comment.
  • User A receives a Slack notification (DM from the Jira Cloud app) stating that User B deleted the comment, even though the actual actor was User 

Expected Results

All Jira and Slack notifications related to the comment deletion consistently show User C as the actor who deleted the comment.

Actual Results

• Jira’s own notification correctly shows User C as the actor who deleted the comment.

• The Slack notification sent to User A incorrectly states that User B deleted the comment, even though User C performed the deletion.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available