The Jira asset picker is great for simple use cases, but it has a drawback – the AQL query is statically defined.  This does not really match real-world scenarios, where databases are often very large while only a tiny fraction of the data is actually relevant in a given fetch context, and the fetch context can change dynamically (even from card to card).

 

E.g. 

I have an Assets database for Contacts, with a field for Company. Separately on Jira I have a Company field on issues representing who the work is being done for.

I want to set up an Contact picker field on my Jira cards. In particular, it should be smart enough to show me only relevant company contacts that I can choose from on any card-- it's completely unnecessary and inconvenient for me to fetch all the contacts. 

 

  Giving us the ability to dynamically pass local context into the database query would greatly enhance its power, and also be more efficient for Jira. Specifically, I want to be able to pass project/issue level data dynamically into the AQL filter for asset picker fields, in order to retrieve only relevant assets to select from.

 

E.g.  I could solve my problem above if I could pass the Company field value from the issue dynamically into the AQL query, say with a smart value reference issue.fields.customfield_....