Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×We've created basic automation that grabs a selection of tickets in a specific status, and posts that list to a slack channel each week. No matter how the slack message is configured, even using the out of the box templates from Atlassian, it's duplicating the slack message.
Automation Configuration:
1. When:Scheduled(Uses JQL)
2. Then: Send Slack Message
Here are the tickets that will be released this Tuesday!
{{#lookupIssues}}
* {{key}} {{summary}}
{{/}}
This results in two identical messages being posted in slack.
"Here are the tickets being released this Tuesday
*issue one
*issue two
*issue three"
"Here are the tickets being released this Tuesday
*issue one
*issue two
*issue three"
Limiting the JQL to the lookup action and excluding it from the scheduled trigger also resolved the multiple slack message issue for me. Thank you @jteamsupport
I actually found the solution.
Make sure that the JQL is not listed in the trigger section, as well as the lookup action. This if I am reading correctly, means that using CRON is no longer an option. I have set my message just to go out daily instead of mon-friday, and it seems to solve the problem.
That said I feel it needs a real Atlassian based fix.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If anyone can help with this I am also suffering from this problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jonathan,
Welcome to the community!
Is the automation rule showing anything in the log? Is the rule triggering more than once? If so I would check the JQL
Best,
Clark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the feedback! The log just shows that it was successful. It ran once. Posted the slack message.
Action Details:
Send Slack Message: Successfully sent slack message.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Actually, I found a work around. Not sure what could cause this.Use the same JQL query. Instead of using it on the "When Scheduled" step, create a new step for "Lookup"
1. When:Scheduled(Just sets the time)
2. Then: Lookup Issues(Use the JQL here)
3. Then: Send Slack Message
Here are the tickets that will be released this Tuesday!
{{#lookupIssues}}
* {{key}} {{summary}}
{{/}}
That works fine.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi I tried this and I still get duplicate messages. Any idea what might have gone wrong here?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey All, I had the same issue and I believe it's because it applies the slack message for on every issue the JQL search finds to apply changes on. So 4 issues found in the JQL = 4x slack messages.
I have fixed it by not having the JQL search in the schedule module but rather have a branch module down the line which includes the JQL search to pull in issues to apply the changes to. I have the lookup module ahead of this and I now only get the single slack message.
Basically you want the lookup issues module ahead of any JQL filter 👌🏻
This screenshot will help explain:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello there. What about the case where no action is to be taken? I simply want the list and I am still getting duplicated Slack messages.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.