AQL Query Across Multiple Object Types Using Attributes and Custom Field Reference

Sathishkumar S_vaoozo

I'm trying to build an AQL query without restricting it to a specific objectType, and instead query objects based on attribute values.

My use case is to search across multiple object types using two attributes:

AQL

"Attr1".Name = "SOME TEXT"

AND

"Attr2".Name = ${customfield_XXXXX.label}

Observations

• The first condition works as expected:

  AQL

  "Attr1".Name = "SOME TEXT"

  It returns matching objects across different object types

• However, when I add the second condition using the custom field reference:

  AQL

  "Attr2".Name = ${customfield_XXXXX.label}

  the query does not return the expected results.

Question

Is there any limitation when using a Jira custom field variable within an AQL query that is not scoped to a specific object type?

Has anyone successfully used a custom field placeholder such as:

AQL

${customfield_XXXX.label}

for attribute matching across multiple object types? If so, are there any prerequisites or alternative syntax that should be used?

Any guidance would be appreciated.

Sathishkumar S_vaoozo

Observation regarding Assets AQL validation in Forms Designer vs JSM Portal

I initially thought there was an issue with my AQL query because the results were not being filtered correctly during testing.

However, after further investigation, I realized the AQL itself was working as expected.

The confusion came from where I was validating the query:

• When testing the field in the Forms Designer preview, the Assets field displayed irrelevant results or nearly all available objects.
• When accessing the same form through the actual Jira Service Management Customer Portal, the field behaved correctly and showed only the expected filtered objects.

So, in my case, the issue was not with the AQL syntax or field configuration. The behavior in the Forms Designer preview did not accurately reflect the filtering behavior seen in the live portal.

Has anyone else observed differences between the Forms preview and the actual JSM portal when using dependent Assets fields and AQL filters?