How to set up AQL to dynamically filter asset custom field across different projects

[IL]

Let's say I have an assets table where each object is associated to a different Jira project  (concretely, let's say I have a column for the jira project key, called project_key, in the assets table to denote the relation).

I want to set up an assets custom field in Jira so that on a particular project, I can select from only the filtered list of assets that are related to that project, and I want this behaviour to hold across many different projects. In other words I want a filter condition kind of like

table.project_key == jira.project.key

Is AQL able to parse smart values like project.key for dynamic filtering? Or is it only scoped to asset properties for now? If so, would there be another clean way to achieve the desired behaviour using asset custom fields?

[Mikael Sandberg]

In order to achieve this you will have to set up a context for each project and then use filter scope in order to limit the object field to only show objects related to the specific project. It cannot be done with smart values.

[IL]

I appreciate the clear answer, thank you. This leads to a follow-up-- do you know if it's possible at this time to automate this process to set up contexts and AQL filters by project via rest API actions? I can square this approach but there'd be a few hundred projects to set up, plus projects where this field should appear will be regularly created on an ongoing basis.

[Joseph Chung Yin]

@IL -

I agreed with @Mikael Sandberg statement.  When one select the custom field (sourced from Assets) against an issue, it will make setting up custom fields based on context a bit more complex process to manage those custom fields.  Unfortunately, there is no dynamic way solution that I know of at this time.

Best, Joseph