nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation + Xray GraphQL error

Helmut Leonhardt

Hi,

I want to user Send Web Request in Automation to change a value in a xray work item.

Like this: updateTestType

I added this as custom data for a POST call.

this result i a 503

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD><BODY> <H1>503 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> The Lambda function associated with the CloudFront distribution is invalid or doesn't have the required permissions. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. <BR clear="all"> If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation. <BR clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: dgrcicHvnwNupgyfGGNfNZwcCayAdYQmx4VSTTRVRPEE__TUiTM0pA== </PRE> <ADDRESS> </ADDRESS> </BODY></HTML>

I think the query is valid, because it works in a respective powershell call from my laptop.

Also the header/token seems to work. Anything I need to consider in Automation?

Accepted answers

Helmut Leonhardt

So this looks like a valid custom data

mutation {
updateTestType(issueId: \"1398108\", testType: {name: \"Manual\"} ) {
issueId
testType {
name
kind
}
}
}

All comments

Gor Greyan_wzwybp

Hi @Helmut Leonhardt

Welcome to the Atlassian Community!

Since the same GraphQL mutation works from PowerShell, the query itself is probably fine. The issue is most likely related to how the request is being sent from Jira Automation.

I would first compare the Automation web request with your working PowerShell request and make sure the following are exactly the same:

POST method, correct Xray GraphQL endpoint, Content-Type: application/json, Authorization: Bearer <token> and the body format.

In Jira Automation, the body should usually be sent like this:

{ "query": "mutation { updateTestType(issueId: \"12345\", testType: {name: \"Manual\"}) { issueId testType { name kind } } }" }

If your mutation contains quotes or line breaks, make sure they are escaped correctly, as Automation can send the body differently than PowerShell.

The 503 CloudFront response does not look like a normal GraphQL validation error. If the request format is correct and it still only fails from Jira Automation, I would suggest opening a ticket with Xray Support, because they can confirm whether requests from Jira Automation are being blocked or rejected on their side.

Check this doc also.
https://docs.getxray.app/space/XRAYCLOUD/44565894/GraphQL%2BAPI

Helmut Leonhardt

So this looks like a valid custom data

mutation {
updateTestType(issueId: \"1398108\", testType: {name: \"Manual\"} ) {
issueId
testType {
name
kind
}
}
}

Gor Greyan_wzwybp

Dear @Helmut Leonhardt

Thanks for sharing the mutation.

Please also verify these points.

- The Content-Type header is set to application/json.
- The GraphQL mutation is wrapped in the expected JSON payload, like this.
{
"query": "mutation { updateTestType(...) { ... } }"
}

- The Authorization header is identical to your PowerShell request.

A 503 CloudFront response indicates that the request reached the endpoint but wasn't processed successfully.

Helmut Leonhardt

query formated as single line:

mutation { updateTestType(issueId: \"1398108\", testType: {name: \"Manual\"} ) { issueId testType { name kind } } }

Helmut Leonhardt

@Gor Greyan our sparkflow instance is only accessable per whitelisting of our company ip ranges.

I guess it same applies from xray itself.

is there anything a administrator has to do so jira cloud automation server is also able to private xray cloud?

Gor Greyan_wzwybp

Dear @Helmut Leonhardt

Thanks for the additional information.

If your Xray endpoint is protected by an IP allowlist, then Jira Cloud Automation may indeed be blocked, since web requests are sent from Atlassian Cloud infrastructure rather than your company's network.

There isn't a Jira setting that allows you to configure the source IP addresses used by Automation. You may need to allow the appropriate Atlassian Cloud outbound IP ranges, or use an intermediary service within your network to relay the request.

Check this doc for the outgoing IPs.
https://support.atlassian.com/organization-administration/docs/ip-addresses-and-domains-for-atlassian-cloud-products/

Atlassian Cloud IP ranges - https://ip-ranges.atlassian.com/

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud