I've got an automation from Jira.
The intention is that every time a deployment happens, the list of issues from the deployment get put into a slack message, and then sent to a slack channel.
What is currently happening is: we get N messages, with N issues in each message. If we've released 10 items in the release, we get 10 messages with all 10 issues listed in each.
What am I missing?
Apologies that you've run into this, we really need to rename these actions as it is a bit deceptive. They should be called issue deployed successfully. The trigger runs once for each issue in a deployment.
This is why you are seeing this behaviour.
Thanks for the information! From that trigger's smart values, it is possible to detect for which issue the rule is running? https://support.atlassian.com/cloud-automation/docs/jira-smart-values-development/
If so, @Quinn Moffat could:
Hi @Quinn Moffat -- Welcome to the Atlassian Community!
Your rule seems to match the same use case shown here for this trigger: https://community.atlassian.com/t5/Automation-articles/New-Build-and-Deploy-triggers-for-Jira-automation/ba-p/1442789
When you look at the audit log, does it show the rule being triggered multiple times for the same deploy?
Hi Everyone, In this roundup we combine all the jira automation rules to sum up story points across different issue types. We start from the lowest level, summing up story points from sub-tasks t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events