Automation JQL condition: using smart values

[Estelle Decanis]

Hi,

When an issue is created, I want to display issues with the same account as the trigger issue.
I'm attaching the documentation on smart values and my automation.

But the "Validate query" light is not activated.
Any ideas?

Best regards,
Estelle

[Bill Sheboy · Accepted solution]

Hi @Estelle Decanis 

The "Validate query" feature is only enabled if the JQL can be determined in the rule builder.  Your JQL is based on a smart value, and so cannot be validated until runtime.

I suggest trying the JQL stand-alone (in View All Issues) with a known value for the field, confirm it works, and proceed from there.

Kind regards,
Bill

[Estelle Decanis]

Thanks for your answer. I'll try

Kind regards,
Estelle

[Estelle Decanis]

@Bill SheboyIf I replace the condition with a value : it works

But if I replace by the smart value

it fails :

The same result with :
Account = {{issue.TempoAccountField.name}}
or
Account = {{issue.TempoAccountField}}

[Bill Sheboy]

Progress!  That tells us the smart value is empty, or not available at the time the JQL is used.

Please try writing this to the audit log, just before your statement using the JQL:

This should not be empty: {{issue.TempoAccountField.value}}

Then test your rule and post an image of the audit log.

Once possible cause of this: there is a known symptom with the Issue Created trigger that it can fire so quickly the issue data is not yet available for the rule to use.  (i.e., a race-track error)  The result is the rule steps do not work as expected / in a predictable manner.

The work-around for this is to always add the Re-fetch Issue Action immediately after the Issue Created trigger.  This will reload the data before the rule proceeds.  Please try that after the above test.

[Estelle Decanis]

if it's correct

it doesn't work

I try with Re-fetch :

@Bill SheboyI must have made a mistake using your instructions

[Bill Sheboy]

Thanks; that rules out a couple of possible causes.  Let's now check if the Tempo documentation is correct...

Automation rules do not support all possible fields.  For example, some fields from marketplace apps are dynamic and may not be supported.

Smart values are name, spacing, and case-sensitive.  And often the smart value does not match the displayed field name on the issue views.  The how-to article below helps to identify the correct smart value (and custom field id) for any supported fields for automation rules.

The essential steps are:

• identify an issue which has your field(s)
• call a REST API function with a browser to search for your issue:

https://<yourinstanceurl>/rest/api/2/issue/<issuekey>?expand=names

• search on the page for your field, such as with CTRL-F
  • if you find the field, you will also find the smart value, custom field id, and structure / attributes it has
  • if you do not find the field, it is not supported by automation rules

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

[Estelle Decanis]

Great !! Thanks !
I fund this :

in the Support/Atlassian documentation there was this example:

I set it up with the id of my field

There's change :)

it's the name of the center looking for.
It found it, but apparently it's invalid. And the action of the automation doesn't work

[Estelle Decanis]

I change the condition :

The center of the trigger issue is identical to that of an existing ticket (this is what I was looking for) :

But it's still marked Invalid JQL :/

[Estelle Decanis]

Bingo ! I fund !!

[Estelle Decanis]

it's a smart value so the condition shouldn't be "jql" but "smart value" :

the action could be done (= link issues) :

Here's the automation :

Thank you so much @Bill Sheboy

[Bill Sheboy]

Well done!

And I see why your JQL condition failed: there are embedded spaces (and other characters) in the values.  The fix for that would be to wrap the smart value in quotation marks for the JQL, like this:

Account = "{{issue.customfield_10044.value}}"

[Estelle Decanis]

Of course !! How could I forget that ?

Thank you so much for yours answers :)