Summary

A WebHook request may fail silently. This may be because:

• The request doesn't reach the recipient
• The request reaches the recipient, but is not supported by the recipient (e.g. unsupported events)
• The request reaches the recipient, but is rejected by the recipient due to unexpected content

In such a case like this, we need to debug WebHooks as well as set up a test recipient to verify whether/how it receives a WebHook request from Jira.

Environment

All versions of Jira Core 7.x and 8.x

Solution

1) Steps to collect data

1. Go to https://requestbin.com/ → Create a Request Bin → Copy the endpoint URL e.g. https://en6a8q2j1l64.x.pipedream.net
    Make sure you uncheck Private (requires log in) before you hit the create button.

2. Create a new WebHook with all the same settings (JQL, events, body included/excluded) as the problematic one, but set the WebHook URL to the endpoint URL above

   • For Service Management Automation WebHooks, add a new WebHook with all the same settings (empty/Jira/custom payload) to the same THEN condition, but set the WebHook URL to the endpoint URL above

3. Go to Jira Administration → System → Logging and profiling → Configure logging level for another package

4. Enter com.atlassian.webhooks for the Package name → Set Logging Level to DEBUG → Add

   • For more verbose logging, enter org.apache.http for the Package name → Set Logging Level to DEBUG → Add
5. Mark the logs as per Marking Jira logs for troubleshooting purposes to indicate Replication Start

6. Trigger the WebHooks (a single event should be able to trigger both WebHooks)

7. Check and see if the request reaches the Request Bin page (where the endpoint URL is presented)

8. Mark the logs again to indicate Replication End
9. Disable the package debugging (temporarily set logging level to None)

2) Sending data to Atlassian Support

Attach the following data to your Support ticket:

1. A screenshot of the WebHooks' settings
2. A Jira Support Zip
3. A screenshot of the request details from the Request Bin page

For Service Management Automation WebHooks, also attach the followings:

1. A full screenshot of the Automation configuration
2. Automation logs