Jira automation , AQL condition with placeholders

Kukk
Contributor
November 10, 2023

Hello!

 

I have customer asset fields on portal request for cascading selection of user assets.

It works well. But i want to make an automation that checks if the connections are valid. 

 

This Filter issue scope (AQL) works on Asset object field configuration

objecttype = machine and partofproject = ${customfield_10074}.

 

In automation i want to do the same check using AQL condition

objecttype = machine and partofproject = ${customfield_10074} - does not work in automation.

 

 

 

1 answer

1 accepted

3 votes
Answer accepted
Rudy Holtkamp
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 10, 2023

Hi @Kukk ,

If you use Automation for Jira, and want to include a field, you should use Jira smart values.

This will turn you AQL clause into:

objecttype = machine and partofproject = "{{issue.fields.customfield_10074}}"

Don't forget to use double quotes. Because if you have spaces in the name/label of the partofproject value, it will not work.

 

Good luck,

Rudy

Kukk
Contributor
November 11, 2023

Rudy! It worked! Thanks a lot that you took the time to answer, i did not make the connection that Jira Automation AQL condition can take smart values.

Like Rudy Holtkamp likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events