-
Bug
-
Resolution: Won't Fix
-
Medium
-
None
-
4.6.0, 4.8.0, 4.13.3
-
18
-
Severity 3 - Minor
-
21
-
Hi Everyone,
Thank you for your interest in this issue.
We have found that resolving this webhook behaviour requires an architectural change to the product. After careful consideration, we’ve decided not to fix this bug and instead prioritise the bundling of the popular Automation for Jira app with the Jira & JSM Data Center platform. This will provide more powerful automation rules that go beyond the current capabilities of Jira Service Management’s automation engine.
Please keep an eye on Atlassian’s public roadmap for the latest updates on Automation for Jira.
Kind regards,
Charlie Marriott
Jira Service Management, Data Center & Server
Issue Summary
Service Desk webhooks that fail because of whitelist or execution failure still indicate success on the UI
Steps to Reproduce
- Create a webhook using SD native automation.
- Make sure the whitelist is enabled.
- Verify the URL used in the webhook is not whitelisted.
- Trigger the webhook in the SD automation.
Expected Results
The triggering of the webhook will fail due to the whitelist and the automation will register it as a FAILURE.
Actual Results
The webhooks fail silently, and the automation marks SUCCESS. When enabling the webhooks package com.atlassian.webhooks in debug level ** a warning with the failure of the webhook appears:
2020-08-04 23:16:36,204+0800 PsmqAsyncExecutors-then:thread-4 WARN rene 1396x1461x1 e4m615 0:0:0:0:0:0:0:1 /rest/api/2/issue/10044/comment [c.a.s.p.a.i.e.engine.asyncthen.AsyncThenJobProcessor] Failed executing ThenAction com.atlassian.servicedesk.plugins.automation.webhook.rulethen.WebhookThenAction asynchronously: 'Invalid URL, not permitted by the system whitelist'
- This issue seems to have started in SD 4.6 when there was a change made to the whitelist, according to Jira Service Desk webhooks
Workaround
Make sure the webhook URL is added to the whitelist.