Placehonder values Invalid inside the "Filter Issue Scope (AQL)" Section

[Alejandro Alcuaz Temiño]

Hi Everyone,

We are currently having a problem making an issue show the correct information regarding our assets.

We just started using this functionality and unfortunately we do not understand it completely.

This is the current situation:

We have a schema called "Facilities" with and objectype called "CDL Venues" inside of it. This object has amongst different fields, the attribute "Country" and "City" inside of it.

Additionally, we also have two different Custom Fields called "Country" and "City" (which are both the following type: Select List (multiple choices)) that we are using for our different request types.

We would like to use assets to improve our requests and thus reducing the errors while creating one.

Our problem comes when we want to filter the venues when introducing the Country and the city inside the issue. We would like to filter the venues appearing inside the asset custom field and our "Filter Issue Scope (AQL)" is giving us the following error: 

What would be the correct syntax to make this work?

Thank you all

[Kai Becker · Accepted solution]

Hi @Alejandro Alcuaz Temiño 

might be just a small update, but I think when using IN you need to encapsulate the placeholder in brackets like 

xyz IN (${customfield_12345})

If you also want to move the Country and City part into Assets, here is a guide on how to filter on another Asset field https://confluence.atlassian.com/jirakb/how-to-filter-assets-object-within-a-issue-based-on-other-object-custom-field-storing-multiple-objects-1142453352.html

[Alejandro Alcuaz Temiño]

Thank you Kai, I will try an set up the new Asset objects, as trying to get the information from Customfields inside the issue is not working whatsoever using the Placeholder syntax.

Let me get back to you once I'm able to stablish it is working properly!

Thank you!