JSD webhook doesn't work when posting to slack

[Gil]

Hi all,

I'm trying to get automation to post to slack channel or a person. The automation trigger, conditions and action pass, but nothing is arriving to Slack.

I know how to setup webhook integrations with slack. All of them are working.

But for some reason, it doesn't work with JSD.

For example: If comment is public and issue status is Closed, then POST webhook.

I then provide the channel webhook URL and trigger the rule, but nothing happens in slack.

Can someone assist?

[Susan Hauth _Jira Queen_ · Accepted solution]

Hey Gil,

I tried everything to make that slack notification/webhook work in JSD.  I finally gave up.  Atlassian blames Slack, slack blames Atlassian.  Please post here if you get any resolution, maybe with a partnership you will get a better answer.

In the meantime, I used the app (Automation for Jira) and it creates beautiful slack notifications, easily and with a lot of granularity and detail.

Hope that helps

Susan

[Gil]

hi @Susan Hauth _Jira Queen_ thanks for sharing your experience.

It's funny. I thought Atlassian and Slack have good partnership, since there's a built-in slack integration within Jira. It's very basic, but it exists and it works well.

It seems that the JSD project with Slack integration is a bit half-baked solution.

I use Automation for Jira as well and it does solve most of the issues.

Gil

[Susan Hauth _Jira Queen_]

Hi Gil,

At the time that the JSD automation and webhook functionality was put in place, Atlassian and Slack were not partners, anything but. 

So I was getting no cooperation from either side on this problem.  Hoping that will start to change.

Cheers,

Susan

[Michael Carolin]

We also dealt with this issue. Slack webhooks require a certain payload JSON key-value set in the body. JSD automation in Cloud does not allow you to modify this body. Instead, JSD will send a body containing the data of the issue associated with the automation rule. You cannot modify this body. Consequently, Slack will return a 400 HTTP error code and a message that says "Invalid_Payload," since Slack requires the payload to include a "text" key and value at minimum. Jira will not show you these error messages, but if you try the webhook in a tool like Postman or with Curl in a terminal, you will see them.

Strangely, Jira Server does let you modify this body, but not cloud.

We are entertaining the Automation for Jira plugin to solve this, or using a service like Zapier to adapt the webhooks together.

[Cat W]

@Michael Carolin thank you!  We're on Server but we're still on JSD 3.11 which does not have the option to modify the payload, and this finally gave me a solid clue as to why we're having an issue with these with Slack webhooks from JSD automation.  We have many in Automation for Jira that work perfectly, it's just one set in JSD that was set up by the project admin and I can just move that to A4J with the rest.

Thanks again!

[Gil]

@Vasi  thank again for your continued efforts in assisting with my questions.

I will contact Slack. Tomorrow I'll have a read about their level of support on incoming webhooks.

[Vasi]

@Gil perfect!

I can also see that you submitted a ticket to Support about it as well :)

We will try to get to the bottom of this!

Cheers,
Vasily

[Gil]

Thank you! :)

It doesn't end there.

I found another bug:

https://jira.atlassian.com/browse/JSDCLOUD-7993

Your support agent raised it on my behalf.

See my comment there as well :)

[Vasi]

Hey Gil,

I did a bit of a research and suspect the following:

I am sure you can check that webhook is working fine and it is triggered.
What I suspect is, based on some previous cases, that webhook that you generate from Slack is a generic one that accepts requests only in a certain format, based on this:
• https://api.slack.com/incoming-webhooks

To clarify that, you might want to get in touch with Slack support.
I am yet to check it a bit more in details and try to test it, however just giving you a thought.

Cheers,
Vasily

[Susan Hauth _Jira Queen_]

Hi Vasily,

I think Gil and I are really hoping that Atlassian can work with Slack to resolve this problem now that there is a partnership agreement.

Susan