Uploaded image for project: 'Automation for Cloud'
  1. Automation for Cloud
  2. AUTO-71

More ways to work with webhooks in Automation - add the ability to send a custom payload or specify a retry policy, read variables from webhook URL, send response on incoming webhooks

    XMLWordPrintable

Details

    • 3
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      At this time it's not possible to customize the payload which is sent on the Service Desk automation for Jira Cloud. On the Server Version we can customize and set some variables as shown on the doc that it follows:

      Jira Service Desk webhooks

      From Jira Service Desk Server 4.1, you can send a custom payload in your automation webhook.

      It would be nice to have this same option on Jira Cloud as well.

       

      ***

      As an Admin, I would like to see Incoming webhooks return a value when they receive a request.

       

      Expected behavior: Sending a request to an Incoming webhook URL will return a result that we can use to determine if the request was successful or failed

       

      Current behavior: The API will always return a 200 code, even when the webhook URL is invalid.

       

      ***

      Problem

      On an Incoming Webhook trigger in Jira Automation, a payload that encloses JSON data in an array "[  ]" will cause the rule to fail with (when parsing the data):

      "Cannot deserialize value of type `com.codebarrel.automation.api.webhook.IncomingWebhook` from Array value (token `JsonToken.START_ARRAY`) at [Source: (ByteArrayInputStream); line: 1, column: 1]"
      

      There is no way to parse the data in Jira as fetching from the payload fails. webhookData is unable to point to the JSON root when enclosed in "[ ]"

       

      • If you send the webhook with a variable, it's not possible to retrieve that information. That causes a system limitation since it's not possible to use the URL variable to create smart values, sometimes it's impossible to find the information we are looking for in the body of the request.

      Attachments

        Issue Links

          Activity

            People

              89403358cf11 Charlie Gavey
              tbehm@atlassian.com Thiago Behm.
              Votes:
              58 Vote for this issue
              Watchers:
              39 Start watching this issue

              Dates

                Created:
                Updated: