Duplicate slack notifications (four of them) for every issue created

[vishal.dogra@rms.com]

Duplicate slack notifications (four of them) for every issue created. We see this on multiple projects. Symptoms started appearing around December 10th and still persist. I also noticed another thread with the same symptoms.

https://community.atlassian.com/t5/Jira-questions/Duplicate-messages-on-Slack-when-creating-tickets/qaq-p/1222480?tempId=eyJvaWRjX2NvbnNlbnRfbGFuZ3VhZ2VfdmVyc2lvbiI6IjEuMCIsIm9pZGNfY29uc2VudF9ncmFudGVkX2F0IjoxNTc5MTE2MjYzNzY2fQ%3D%3D

It appears the issue fixed itself for them but still lingers on for us and is annoying. Could someone please help us with this.

[Daniel Eads · Accepted solution]

Hey Vishal,

Welcome to the Community! We've done some precursory checks on your Atlassian account but haven't yet found the cause of the duplicate notifications you're seeing.

Would you be willing to:

1. Share a screenshot of one of the Slack channels showing the multiple notifications for an issue
2. Confirm the Jira Cloud site you've got connected to your Slack (e.g. something.atlassian.net)

These will help us pin down what's going on more specifically. If the details are not something you're comfortable with sharing on Community, you can email me directly at deads at atlassian.com

Thanks,
Daniel | Atlassian Support

[vishal.dogra@rms.com]

Thanks Daniel for responding. I will be sharing aforementioned details over email shortly.

[Daniel Eads]

Vishal,

Thanks for sending the details via email! Based on the info, we were able to determine that you're using Jira Server for Slack on a Jira Server instance - I've re-tagged this question to note that it's about Server instead of Cloud.

The good news is that it looks like what you're seeing in your screenshot was patched out as a bug in version 2.0.6 of the Server app. If you update the Jira Server for Slack app from the Manage apps page in Jira Administration, the issue should be resolved.

Cheers,
Daniel

[vishal.dogra@rms.com]

Thanks Daniel for details and correct tagging. Will work with our JIRA Administrator on this and get back. Hopefully it shall solve it for us.