Radio Button values in conditional logic

[Anthony Pugliese]

Hi All

can't for the life of me work out what is wrong with my automation and i am sure its simple

I have a form that has a radio button selection

- Option 1

- Option 2

this field isn't connected to a jira field and therefore i have given it a field key as RequestType

when i try to use this in an automation with logic, i cannot seem to get the values working

in the automation i have an IF/ELSE logic whereby

{{forms.RequestType.label}} equals Option 1 (have tried as "Option 1", "Option_1")
then send email with specific description

else, send an email with different description

any help would be appreciated on what the true output should be

[Marc -Devoteam- · Accepted solution]

Hi @Anthony Pugliese 

What is the name of the Radio button field in the form?

USe {{forms.last.<name-of-radio-button-field>.label}} as smart value

[Anthony Pugliese]

it is RequestType
as per another comment below, ive tried that as well as that doesnt seem to work

[Trudy Claspill · Accepted solution]

Hello @Anthony Pugliese 

Can you confirm this related to a form in a Service Space? Is it Team-managed or Company-managed?

Sometimes unexpected rule results have to do with the context of a step. Can you provide us with screen images that show us your entire rule?

Is the rule using the Forms Submitted trigger? That is a prerequisite to using the {{forms}} smart value to access the fields in the form. If not the you have to use a different method, as described in this documentation.

https://support.atlassian.com/jira-service-management-cloud/docs/access-smart-values-for-forms-and-form-fields/

What result are you getting when the radio button is set to Option 1 vs. Option 2?

Have you tried adding a Log action directly before the IF block to print into the rule log the same smart value you're trying to use in the comparison?

[Anthony Pugliese]

it is a company managed space and a screenshot of the automation is below

when i run the results, it says the condition not passed  

Option 1 is actually "New Request" in my automation and form (i was using option 1 to make it more generic in my original post)

[Trudy Claspill]

Thank you for the additional information.

Can you add a Log action before the IF block to print into the log the smart value you are using in the condition? And then run another test to trigger the rule and share the results with us.

[Anthony Pugliese]

@Trudy Claspill , i've tried a few scenarios using this [New Request] whether within brackets or not

[Trudy Claspill]

Is there more than one form being submitted?

Can you try...? {{forms.last.RequestType.label}}

Or

{{forms.first.RequestType.label}}

[Anthony Pugliese]

no more than 1 form being submitted

ive tried both of those scenarios and i get the same issue where it says the condition not passed 

[Anthony Pugliese]

@Trudy Claspill 

in the end i found a way, using a create variable action using {{forms.last.RequestType.label}}

then configuring the IF statement to use the variable instead of the form field

[Trudy Claspill]

Hello @Anthony Pugliese 

I'm glad you found something that works for you

However, I have not been able to recreate the issue you encountered. Using {{forms.first.RequestType.label}} directly in the compare in the IF block works for me. It fails only when I use {{forms.RequestType.label}} without including ".first" or ".last"

[Anthony Pugliese]

@Trudy Claspill 

thanks. i re-ran the same scenario and the same issue appears. for now i have a workaround

thanks for the help