Issue Summary

JSD's Automation webhooks behave differently to Jira webhooks when using Jira behind outbound http-proxy. Jira webhooks respect the NonProxyHosts configuration while Service Desk webhooks always go through the proxy. This can also lead to a scenario where using JSDs automation to fire webhooks, they look like they are sent, but they timeout and/or fail silently.

Steps to Reproduce

1. In the setenv.sh/.bat we set additional JVM arguments (JVM_SUPPORT_RECOMMENDED_ARGS) with:
   • http.proxyHost
   • http.proxyPort
   • http.proxyUser
   • http.proxyPassword
   • https.proxyHost
   • https.proxyPort
   • https.proxyUser
   • https.proxyPassword
   • https.nonProxyHosts
2. Add a JSD automation that triggers a webhook.
3. Perform an action that triggers this automation rule.

Expected Results

The web request is sent through the proxy configured in the JVM arguments and reaches its destination.

Actual Results

The webhook is triggered, but it does not follow the proxy configuration and does not go out of Jira, failing silently.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available