Send Slack message via Automation suspecting outdated incoming webhook configuration

[Albert AG]

Background context:
We would like to have an automated message sent to a specific channel in Slack, when a specific issue(we filter it with JQL and validated) is transitioned from TO DO to IN PROGRESS.

Current situation: Though the integration has been set, I have no clue why the automated message are not sent into the specified channel.

Here are the step by steps I made earlier:

I got into this Automation page, it explained the step by step very well.

The next step is how do I get this webhook URL, I follow the link provided in here.


Getting into the provided link, do a simple step by step in this page, and save settings.

As I go back to my Slack channel, I see the integration has been addded.


Then I tried to move a specific card that are matched via JQL that has been previously defined in automation page (first image above), There are no upcoming message sent to the channel.


Is there any way to solve this issue? or other alternative to do what I look for sending automated message when a issue card transitioned from TODO to IN PROGRESS?

Tuspecting issue might be in "configure an incoming webhook" as it is stated that this is a legacy custom integration/an outdated way to integrate with slack.

[Daniel Eads · Accepted solution]

Hi @Albert AG , welcome to the Community!

The question about the Legacy webhook app comes up with some regularity. This is currently the way to use Automation with Slack. Although the app is deprecated by Slack, the replacement app does not provide a way to override the default configured channel, which is a key feature of the current implementation in the Legacy Incoming Webhooks app. AUT-1515 contains the information about a possible change for this in the future.

As for why a message didn't send to the channel, I would recommend checking the Audit Log (on the left side of the rule setup, underneath the name and Rule Details options) for the rule to see if the previous runs matched your conditions. You can expand the details for rule executions to see if a particular issue met the criteria defined in your rule.

It's also worth checking the status names - in your description here on Community, you wrote "TODO", while the Automation rule is set to match "To Do". The addition or removal of a space can make or break the trigger.

Finally as a quick alternative, with the trigger and JQL condition you have defined, I believe you might actually be able to use the native Jira Cloud for Slack app if you wish, instead of Automation for this purpose. You'd want to continue working with Automation if you needed to send a customized message into Slack or run more complicated measures such as branching conditions. The rule you've got though is a good candidate for the native Slack integration, which you can access from a project's settings. You might use a configuration like this:

Cheers,
Daniel | Atlassian Community Support

[Albert AG]

Hey @Daniel Eads ,
Thank you for your quick response.

A very helpful help checklist mentioned by you is checking the Audit Log. That it bring me to the root cause tracking for the problem.

And yes I found the root cause because the status named between "To Do" and "TODO" where right now we have several boards and I wrongly took the "To Do" for different board.

Now it works, thank for your help!