How to use form checkbox value in automation rule

[Kris Dewachter]

Hi all,

I have the following problem.

I have a JSM form, linked to a request type.

The form contains a "checkbox" field, with 1 option.

When the form is submitted, a ticket is created.

I created an automation rule, that creates a new sub-task, and I want to include a special note in the sub-task description, when "Authpoint = Yes"

I can display the value of the checkbox with this smartvalue :

{{issue.forms.e4d301e5-8d86-4b14-8b1a-df2f81b4cfeb.authpoint.label}}

The returned result is [Yes]

And now my problem is that I can not get this working in an <if> statement. I tried following:

{{#if(issue.forms.e4d301e5-8d86-4b14-8b1a-df2f81b4cfeb.authpoint.label,"[Yes]")}}

{{#if(issue.forms.e4d301e5-8d86-4b14-8b1a-df2f81b4cfeb.authpoint.label,"Yes")}}

Any idea on how to build an <if> statement, based on the value of the checkbox ?

Best regards,

Kris

[Marc - Devoteam]

Hi @Kris Dewachter 

When you make the values visible in the sub-task, by using the smart values, the result visible in the sub-task is now just text.

So you will need to use smart values to find is text values Yes is on the issue.

Or another solution would be to copy the whole from from the parent to the sub-task, then you could use the smart values form options.

[Bill Sheboy]

Hi @Kris Dewachter 

Yes, and...for the suggestions from Marc:

As the value is text, you could use the equals() function inside the conditional expression: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#equals-string-

And, I have noted in some community posts there can be latency accessing form data with smart values.  If you encounter this, the workaround is to first store that field's value with a Create Variable action, forcing it to fully evaluate / lookup, and the use the variable in the test.

Kind regards,
Bill