+1 Please investigate this issue

this is likely related to single-voted but more specific problem of different payload schemas used in transitions and other events: https://jira.atlassian.com/browse/JRACLOUD-78163

Anyway... Severity - Major, Priority - Medium, Atlassian - it is just 7 years old, it is still so young!

+1 please investigate this issue. 

Hi there,

I am trying to integrate Webhook with my project, i have created webhook created route for it, and route is woking fine with boht post and get. However the webhook is not triggering and thing to the provided url.
 Help will be appreciated.

Thanks

+1

Would very much like to have this feature.

+1

This is needed please

+1

This is needed please

+1. 

Severity 2 - Major, Priority - Medium.

5.5 years later... @Atlassian: gathering impact.

Too bad.

this is a really needed feature. kindly help prioritise. thanks

+1

For those using MS Teams.  The transition webhook won't work.

The webhook is definitely sending.

The issue is that JIRA is sending a different JSON response when doing it from a transition , vs those checkboxes.

I hooked up the webhook to a https://webhook.site/ and when I pushed the response along to to MS teams - I got "Webhook Bad Request - null or empty eventType" - which it doesn't have

Only the ones triggered from "created, updated" have this metadata.  I assume MS Teams integration is serializing a certain response, and since it differs, they blow up.

+1

Seeing the same behavior

Hi there, just a reminder, this is a feature that is 100% impaired and does not function as advertised.  Would love to see faster than 4 year response times for things of this nature!

+1

+1

We are experiencing this issues as well. I noticed that my issue is being caused be the content-length header... in my case, this came from the webhook as 29212... which was incorrect as the body of the post call was actually 37553. This only seems to occur on the Transition trigger of a webhook.

Steps to reproduce:

• Configure your webhook to point to webhook.site. When triggered, take note of the content-length header captured by webhook.site.
• Use Postman to post to the same endpoint, both with and without the content-length header and value. Expected results are 200s without, and 400s with.
• Copy the body from webhook.site to http://string-functions.com/length.aspx ** to calculate the real length of the body. 
• Try Postman again with new value... 200s again.

Same issue here. Webhooks fire in response to events (original system events) but will not fire when triggered by workflow.

Same issue, against the MS Teams webhook. If I switch the webhook to be triggered by an Issue, updated event, it works and I get the post inside Teams (this proves it's not an https issue, or bad url). If I remove the event, and make it trigger on a Transition, via a "Resolved" Post Function, it doesn't fire.

I've tried to move my Post Function above or below the other Post Function "Fire a Issue Resolved event that can be processed by the listeners", no difference.

A possible resolution for this one would be to have an event for "issue resolved" in the event section. But it won't help for other custom workflow transitions.

Note: the documentation at https://developer.atlassian.com/server/jira/platform/webhooks/ in the Known Issues section is incorrect. It states:

• Post function webhooks do not fire if added to the Create Issue workflow transition. We recommend that you configure your web hook to fire from the issue_created event instead.

However, it's for all transitions, not just "Create". Would be good to link to this ticket as well from there.

We have this on server instance too, will open another ticket. version 7.5

Hello, I am experiencing this issue. Trying to call an azure endpoint in my Jira webhook and I am getting nothing in Azure according to logs. I am able to publicly post to my endpoint.

I think we're seeing it too. The same webhook works fine if attached to an event, but not if attached to a transition.

I believe I'm seeing this as well. So it appears that the entire post-function for triggering webhooks is broken right? I can't get the webhook attached to a transition to fire at all....

We're using the following workaround - when the external system accepts the new info, it sends back to JIRA  the text fileld SUCCESS. and we empty this field at every transition right before triggering webhook. So if webhook worked SUCCESSfully, this field is never empty.

Afterwards in all the cases when the success-field is empty (JQL filter) , the external system 'asks' JIRA to send the tickets again - and we do this check by job every 10 minutes.

So we have 2 integration flows from jira.

Hi Team, 

We are facing the same kind of issue, time interval for the data is not updating(WebHook) is "12:00 Am IST to 5:00 AM IST" 

Please check and resolve the problem immediately. 

Regards,

Shankar. E

91-9884957983

Hi, we are experiencing this issue too, has there been any update?

Thanks,

Paul