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

            [JSDSERVER-6789] Webhooks from Service Desk automation do not follow proxy logic

            Hi, our main issue is not to intergrade Microsoft teams and Jira but to understand how we can generate our dashboard from the Sprint planning.

            Umee Balqes binti Ameer Wahid added a comment - Hi, our main issue is not to intergrade Microsoft teams and Jira but to understand how we can generate our dashboard from the Sprint planning.

            f70a55a1e805 this bug report is related to a Service Desk behavior when using a proxy and is hosted on a public bug tracker. A request like yours is better handled by Atlassian support (https://www.atlassian.com/company/contact), but I want to mention that Jira does not support Microsoft teams natively, and consultancy services are not part of Atlassian support offerings. If you have questions regarding what options are available to integrate Microsoft teams with Jira, the best is to check the Atlassian marketplace and to contact the vendors of the plugins that might provide what you need. You can find them here: -

            Rene C. [Atlassian Support] added a comment - f70a55a1e805 this bug report is related to a Service Desk behavior when using a proxy and is hosted on a public bug tracker. A request like yours is better handled by Atlassian support ( https://www.atlassian.com/company/contact ), but I want to mention that Jira does not support Microsoft teams natively, and consultancy services are not part of Atlassian support offerings. If you have questions regarding what options are available to integrate Microsoft teams with Jira, the best is to check the Atlassian marketplace and to contact the vendors of the plugins that might provide what you need. You can find them here: -

            Kindly block a session with JIRA support as we need to explain on our requirement.

            Umee Balqes binti Ameer Wahid added a comment - Kindly block a session with JIRA support as we need to explain on our requirement.

            We seek an online briefing session using Microsoft Team to understand Jira software on how to retrieve our required Project Dashboard Report

            Umee Balqes binti Ameer Wahid added a comment - We seek an online briefing session using Microsoft Team to understand Jira software on how to retrieve our required Project Dashboard Report

            Hi all,

            as this is having a major impact on the OpsGenie Integration (in this case, used to monitor SLAs), can we please bump the priority?

            Daniel Zauner added a comment - Hi all, as this is having a major impact on the OpsGenie Integration (in this case, used to monitor SLAs), can we please bump the priority?

            Hi Team, Can we move this to Bug?

            JSD Automation webhook was working in Jira 7.13.x version, but stopped working from 8.5.x version. That breaks one of our important integration.

            020-04-11 17:33:08,739+0000 PsmqAsyncExecutors-then:thread-192 WARN <hidden_user>   [c.a.s.p.a.i.e.engine.asyncthen.AsyncThenJobProcessor] Failed executing ThenAction com.atlassian.servicedesk.plugins.automation.webhook.rulethen.WebhookThenAction asynchronously: 'Unable to obtain status code from webhook server: Connect to <hidden_url> failed: Connection timed out (Connection timed out)'
            

            Aswin Achuthan added a comment - Hi Team, Can we move this to Bug ? JSD Automation webhook was working in Jira 7.13.x version, but stopped working from 8.5.x version. That breaks one of our important integration. 020-04-11 17:33:08,739+0000 PsmqAsyncExecutors-then:thread-192 WARN <hidden_user>   [c.a.s.p.a.i.e.engine.asyncthen.AsyncThenJobProcessor] Failed executing ThenAction com.atlassian.servicedesk.plugins.automation.webhook.rulethen.WebhookThenAction asynchronously: 'Unable to obtain status code from webhook server: Connect to <hidden_url> failed: Connection timed out (Connection timed out)'

              14858f4147da Nafis Faramarzi
              rchiquete Rene C. [Atlassian Support]
              Affected customers:
              9 This affects my team
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: