-
Suggestion
-
Resolution: Unresolved
-
None
-
0
-
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.
- is duplicated by
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
[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
I'd also like the capability to use smart values in the webhook URL.
It would allow me to send to a different Teams channel depending on what Team the Jira issue is in.
Would be great is webhooks could receive json arrays as payload. Would enable us to start automations in Jira from other systems (for example Hubspot).
Webhooks already have retry policies; I'd love to see retry capability built in to web requests via automation, it would help my current use of some of our automation rules tremendously.
Hi Amaresh,
First of all thanks for identifying & taking up this issue.
I am a Service Manager, I am exploring JSD cloud to implement it in our organization, this is a must have feature for us as we need to update Client's ticketing system once we close a ticket from our end, We need to close the ticket in their system also we need to update the resolution.
So this will be a very helpful feature for us.
Regards, Anil
Hi Amaresh,
typically we want to use this for monitor escalations from Service desk triggered by our specific customer (defined by Automation rules). Service desk agents want to use this for SLAs time expiration monitoring. They have plenty of emails and standard dashboards and they can get better focus in global overview by this feature.
Ability to customize payload with SD issue varibles (like issue type, number, request type, priority, description, summary, priority, approver etc..) will be nice too.
Hi everyone,
This is something we'll be taking on in the next few weeks. I'd be curious to hear about your use cases to make sure we build the right thing. If you have any input, please don't hesitate to send me an email: amaresh.ray at atlassian.com
Amaresh
I agree that this would be a great feature to have in the cloud version. I am not sure why this functionality should be limited to the server version.
We need to be able to accept json payloads from third part systems in order to create issues inside Jira and follow the processes in our Technology organisation.
Most of the time those payloads will contain arrays which currently results in an error:
Cannot deserialize value of type `java.util.LinkedHashMap<java.lang.String,java.lang.Object>` from Array value (token `JsonToken.START_ARRAY`) at [Source: REDACTED (`StreamReadFeature.INCLUDE_SOURCE_IN_LOCATION` disabled); line: 2, column: 11] (through reference chain: com.codebarrel.automation.api.webhook.IncomingWebhook["data"])
This limits the capabilities for automating processes that includes third party systems feeding data into Jira.