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; } } }

Webhooks not calling

fyj ham

I've been trying to test out webhooks from JIRA for an integration. I'm trying it out on a trial account, but I've set up the below webhook to a mock endpoint just to do initial validation but I've not seen any data received on the endpoint despite updating issues & adding comments/attachments.

I've checked with Postman that my mock endpoint is logging posts & it is.

I've tried setting up the webhook both through the UI and also through posting to /rest/webhooks/1.0/webhook - I have no idea why it's not calling my endpoint or what I can even check next. I originally had a JQL query on it for a specific project, but I dropped that just trying to get absolutely anything to work...

I have no idea what I can even check next?

Config from webhook:

Accepted answers

Mohanraj Thangamuthu

Hello, Good day. I confirmed that your domain name is resolving to IP address, this could be an issue on your receiving end (like firewall). To confirm the the same, change the URL to webhook.site URL on the same configured Webhook, replacing your demo url. https://webhook.site/#!/view/4c6d3dee-6cd4-48d1-b303-4622e7a6ca8e

All comments

Mohanraj Thangamuthu

fyj ham

That worked, thanks!

I think the root problem was the unexpected querystring parameter triggeredByUser, I didn't see that in the doco so my mock endpoint wasn't set up for that (Mockable is very picky about the receiving endpoint spec to capture the requests, so it was probably ignoring it due to that - it's a bit more about mocking than just testing/logging).

I do definitely like webhook.site, that one's going in the collection for quick testing in future.

Niklas Malmberg

Nice suggestion with webhook.site, I used it for testing an issue I have.
However, company firewall rules prohibited me posting to that site

I've run into problems when Microsoft recently announced that they will change the Webhook URLs per 31 Dec 2024, and Teams urged me to update to new connectors.

So I created new webhooks and updated my automation rules.
The Jira rules engine recognizes that there is a difference between "old" webhooks and "new" (not sure how that really works, but not that important).

Once I updated, Teams stopped nagging about the need to update.
Jira is happy and write to audit log that the message was sent successfully to Teams.
However, the notifications from Jira just vanish now, receiving Teams channel is quiet. Too bad. Thanks for all the fish, Microsoft.

I have not yet found any explanation or remedy for this.

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-cloud

webhook

jira-cloud-administration