Assets AQL filter stopped to work

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!

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 

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.