Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Slack Notification Shows Wrong User for Jira Actions

Alan O_Driscoll
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 9, 2025

Hi there, just wondering if this is a known issue with Jira Slack notifications where the notifications are showing incorrectly. An action performed by User A (Dave), but is mentioning User B (Alex) who is not watching/assigned/attributed in any way to the task. Seen a number of instances of this and seems to be always when User A - Dave updates a ticket, the notifications show from User B - Alex. Other ppl at my company have come across this. 

No service accounts are involved, history tab on this given task shows User B - Dave performed the action so seems specific to slack integration/notifications. Stumped, any help would be greatly appreciated. 

 

Screenshot 2025-05-09 at 8.03.13 AM.png

 

Thank you

 

 

 

1 answer

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 9, 2025

Hi @Alan O_Driscoll -- Welcome to the Atlassian Community!

What is the source of the notifications messages?

For example, if they are being added by an automation rule, perhaps the rule is mentioning a different user than the initiator of the action.

Kind regards,
Bill

Alan O_Driscoll
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 23, 2025

Sorry for the delay Bill. Our team isn't aware of any automation rule in place  🤔

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 23, 2025

Hi, Alan!

Perhaps look at an example work item with this symptom, checking its history and the automation log to determine if a rule caused the message.

And if not, ask your Site Admin to submit a ticket to Atlassian support to take a look: https://support.atlassian.com/contact/#/

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events