nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation Is Posting Duplicate Slack Messages

jteamsupport

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"

Accepted answers

All comments

Clark Everson

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

jteamsupport

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.

jteamsupport

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.

Mithila N Bhat

Hi I tried this and I still get duplicate messages. Any idea what might have gone wrong here?

Elliot Jones_wpplqa

If anyone can help with this I am also suffering from this problem.

Elliot Jones_wpplqa

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.

Derek Owens

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud