Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Replacement Assets AQL query for connectedTickets() function when nested within the inR() and outR()

Ram Chavan
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 1, 2025

Hello,
We have been using the AQL function connectedTickets() nested within the inboundReferences() or outboundReferences() in Jira Automation

Automation run actions on the objects found by an AQL.
Recently it has been observed that it is not supported anymore.
Can someone please help to provide any other function within AQL which can replace below AQL query with same results.

(object having inR(object having inR(object having connectedTickets(key = {{{{issue.parent.key}}}})))

1 answer

1 accepted

1 vote
Answer accepted
Tommaso Gionfriddo _Adeptask_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 2, 2025

It's not possible to achieve the desired outcome in a single AQL query.

However, because you are doing this in an automation you should be able to split the query into two parts, and pass the result from the first query into the second query.

Example

Lookup objects action 1

object having connectedTickets(key = {{issue.parent.key}})

Lookup objects action 2

object having inR(object having inR(key in ({{lookupObjects}})))

 

I notice that your example is also wrapped in brackets/parenthesis. I'm assuming this is because you've only included a particular section of query.

If this is the case, and you have one query with multiple cases of connectedTickets() nested inside inR(), then you will need to adapt my example to save {{lookupObjects}} to a new variable each time connectedTickets() is run.

The one exception to this is if connectedTickets() is run with the same input JQL, eg. if it's always connectedTickets(key = {{issue.parent.key}}). In this case you can re-use the same result, instead of needing to run the same query multiple times.

 

Ram Chavan
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 5, 2025

Thanks @Tommaso Gionfriddo _Adeptask_ , your fix works.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events