Jira Automation is Spamming Our Slack Channel

[Ran Craycraft]

I set up an automation to send a Slack message when there's a successful Deploy on CircleCI. It's running when expected, but instead of sending the message once, it's spamming our Slack channel depending on how many JIRA issues were in that deploy.

So if there were 9 issues successfully deployed, it's sending the message 18 times in Slack. Any tips on how to just get a single message when deploy succeeds?

[Joy Chiu]

@Ran Craycraft Can you double-check how many issues are included in one deployment? The slack message is sent per issue rather than per deployment. Take an example, if the deployment includes 3 issues, you will receive 3 messages.

[Ran Craycraft]

Thanks for the note, @Joy Chiu . Ok, we can probably work around that. I changed the message, but it's definitely doubling up posts to Slack.

Here's what I mean:  

[Ran Craycraft]

@Joy Chiu I can confirm it's doubling up the number of issues broadcast to Slack. We suspect it's because:

We are currently sending events to Jira from CircleCI.
As we are deploying components to two platforms in each environment (Firebase & Kubernetes), the Jira automation is triggered at the end of a successful update on each platform causing 2x as many notifications in Slack.

Any tips?

[Joy Chiu]

@Ran Craycraft  It depends on how many times CircleCI sends events to Jira. I'd think Jira receives the event twice, so the message is sent twice.