Update Issue with Labels which depend on User Input gathered when manually triggering an Automation

[Rob Rademeyer]

My automaton essentially follows these steps

1. Manually triggered
2. Ask for input from the User (check/uncheck a single checkbox)
3. Log the value selected (so I know it's working)
4. If the checkbox is checked, add Label 1
5. If the checkbox is not checked, add Label 2

I simply cannot get this to work :-<

The User Input is working correctly and I am able to trap the value i.e. True or False.

Then when I want to get the appropriate label added to the Issue, I create an IF block and test for my User Input, followed by a THEN block which adds the appropriate label.

I have tried many different versions of this process but none of them work - I always get a "The following issues did not match the condition: XX-YYYYY" in the Audit Log, and the Label is NOT added.

Any suggestions?

[Hans Polder _Devoteam_ · Accepted solution]

Hi Rob,

Welcome to the community!

The issue is that you're using: {{issueInputs.sanctionYesNo}}

Where it should be: {{userInputs.sanctionYesNo}}

Can you test this change? :)

By the way, when testing this in my own environment it seemed to make more sense to simply choose for a Dropdown rather than a checkbox (if I understood you correctly, you were using that?). If you can't get the rule to work after applying my suggestions above, please share more details (screenshots) on how you've configured exactly your Trigger.

[Rob Rademeyer]

Sigh...

Appreciate your prompt reply, Dan!

I am in my one millionth iteration of this rule so that Smart Value is simply a typo (you will see from the Log step above that I understand how the Smart Value should be referenced) :-<

Bizarrely, the rule now appears to be working. I am at a loss to explain why as I am (pretty) convinced that I was using the correct syntax before. 

What is different is that I am now using an IF/ELSE block instead of a simple IF in a linear chain. I am going to try it my old way and let you know if it works.

BTW, interested to hear your rationale for using a drop-down list for what is essentially a binary action. It's an extra click and while it gives you a distinct string as an outcome, I can't see the advantage for processing a IF statement?

Thanks again; will provide feedback shortly...
R

[Hans Polder _Devoteam_]

Hi Rob,

Glad to hear that it works now!

Scratch my previous comment about choosing a Dropdown over a Checkbox. When I was recreating it on my end I didn't really (yet) understand how you arranged it on the Trigger section. I thought you initially had two checkmarks (one for Yes, one for No), which obviously doesn't make sense 😁.

You indeed don't need to have the IF/ELSE block. It works perfectly fine as a linear automation:

Best regards,

Hans

[Bill Sheboy]

Hi @Rob Rademeyer -- Welcome to the Atlassian Community!

First thing, what problem are you trying to solve?  That is, "why do this?"

The rule steps you describe could more quickly be done by manually adding / removing the label, so knowing what problem this solves may help the community to offer better suggestions.

Until we know that...

This could be done in one step, using an inline condition expression: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-conditional-logic/#if

Let's assume the values of your manual trigger's field are Boolean for the checkbox.  You could use the Edit Issue action to select the Labels field, select the ... option at the right side for ADDREMOVE of labels, and then enter this smart value expression:

{{if(userInputs.sanctionYesNo, "Label_1", "Label_2")}}

When it appears below the field, select it for use, and the test your rule.

Kind regards,
Bill