You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We started getting three Slack messages for every ticket created. Other JIRA notifications work as expected.
We haven't changed the integration settings and there is only one instance of the integration enabled in the channel.
Any pointers on how we can fix it?
Hello @alicja_raszkowska ,
Welcome to the Atlassian Community!
The behavior you are reporting seems similar to the one described in a bug we have already fixed:
However, in the last comment of above bug ticket I can read:
We had the same issue, Then I tried/jira info
on the channel that I was getting duplicate messages on and clicked on the link (Manage Subscriptions). we had two subscriptions to the same project under project subscriptions subscribed by the same channel. Deleted one of them and we no longer receive duplicate notifications from Jira.
Can you kindly check if that's the same case for you or if it is something different?
In case that's not the same case. Can you send a screenshot of the configuration screen?
I checked the issue you linked, but there is only a single integration in our Slack.
Regardless, the issue seems to have resolved on its own since I reported it. We haven't seen multiple create messages in the past week.
Maybe it was a temporary race condition or connectivity issue with the Slack API?
I'm not sure if it's worth digging into since it seems transient. I'll post if it pops up again.
This issue started happening to us starting on April 26th. We made no changes to either Jira or Slack. In the morning it was posting just one message to Slack then midday is inexplicably started double posting on ticket create.
Any new channel we try to test it on also does the same. We have no mail handlers. We are upgraded beyond the version it is said to have fixed the issue. Anyone have any other idea?