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; } } }

Assets AQL filter stopped to work

Enrico Ponchio

Hi.

I have an asset schema with that have some attributes as object tha point to another schema.

Screenshot 2026-09-03 160218.png

I have a filter in that attribute ( Vendor = ${Vendor}).

Until today it worked perfecty.

Today I've seen some new UI improvements and it stops to work.

Anyone with the same problem?

Any suggestions?

Thank you

Accepted answers

Enrico Ponchio

Now it seems that Atlassian stepped back and it works.

All comments

Andrea Robbins

You can remove the parenthesis. If it's in another schema, ensure someone didn't uncheck the box, "Allow others to select objects from this schema" within schema settings.

If the above doesn't work, I would send in a ticket to Atlassian support: support.atlassian.com, click on Contact Us -> Technical issues & bugs -> it will make you ask AI first, but then you can talk to a live person or submit a ticket. It may be a bug and nothing to do with your AQL.

Jovânio Junior

Hi Enrico - Welcome to the Atlassian Community!

Since this was working before the recent UI change, I would first rule out a configuration change before assuming the AQL itself is wrong.

For an Object-type attribute, Atlassian still supports filtering the available referenced objects using AQL. If the referenced objects are coming from another schema, also check that the target schema still allows objects to be selected from other schemas.

I would verify these points:

Confirm that “Allow others to select objects from this schema” is still enabled on the referenced schema.
Try the filter without unnecessary parentheses, for example:

Vendor = ${Vendor}

Confirm that Vendor is still the exact attribute Name. Atlassian notes that AQL resolves against the entity/attribute name, not the newer display name.
If this is actually being used in an Assets custom field, make sure the placeholder is configured in Filter work scope (AQL) and not Filter scope (AQL), because placeholders are not supported in Filter scope.

There is also another Community report from today describing the same behavior after the UI update, so if the configuration above is unchanged, this may indeed be a regression rather than an AQL mistake.

If all of those checks pass, I’d raise it with Atlassian Support and include the previously working AQL plus the approximate time when the new Assets UI appeared.

Hope this helps!

Enrico Ponchio

The correct filter is Vendor = ${Vendor} and it worked perfectly until the change Atlassian made.

Enrico Ponchio

Parenthesis () are only made by the copy/paste.

The correct filter is Vendor = ${Vendor} and the box is checked.

It worked until GUI update.

Enrico Ponchio

Now it seems that Atlassian stepped back and it works.

Andrea Robbins

Glad they seem to have rolled it back but I do think it is related to the display name vs the name. If you update it to the name and not using the display name in the future that would be best. Display name can’t be used for anything but viewing in the UI. I had to update a script of mine as well

Enrico Ponchio

I've tried:

Name = ${Vendor}

Vendor = ${Name}

Then only way it work is Vendor = ${Vendor}

There is a

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management