Forums

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

What is wrong with AQL?

Antonia
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 Champions.
December 12, 2025
( (objectTypeID = 194 AND objectId = 686) OR (objectTypeID = 236 AND objectId NOT IN (20700, 72507, 71333, 20683, 20765, 20757)) ) AND "Hardware-Status" = "aktiv"

 

So:

The object is of type ID 194

AND it has object ID 686

AND the hardware status is “active”

Then a Ticket should be created, every second tuesday. (this is from a rule)

And also the object is of type ID 236

AND the object ID is NOT in the list (20700, 72507, 71333, 20683, 20765, 20757)

AND the hardware status is “active”

I wanted to link the different object type IDs, i.e., 236 and 194.

So in 194, a ticket should only be created for ID 686. And in 236, a ticket should be created for every asset except those included in this list/enumeration. And all assets should have the hardware status “active”; otherwise, no ticket should be created.

 

When I split the AQL in two requests it is working, but I have to go in to the different object types..

 

Could it be that I have to create two rules because there are two different object type IDs?Screenshot 2025-12-12 111557.png

0 answers

Suggest an answer

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

Atlassian Community Events