Automation not working as expected with multi-select custom field

[Durell Demartini]

Hello all,

We're using Jira Automation to create sub-tasks. We have a custom field of type multi-select called, "Type of Modify" with options "Storage" and "Compute." Within the automation rule, we want to build logic that IF "Storage" is selected then generate a sub-task for Storage, or IF "Compute" is selected then generate a sub-task for Compute. IF both options are selected, then generate sub-tasks for both Storage and Compute.

Here are the conditions for the custom field:

• contains any of
• contains all of
• contains none of
• equals (in any order)
• is empty
• is not empty

I've used the condition, "contains any of," and it is working successfully when both Storage and Compute are selected - both sub-tasks are getting created successfully.

However, when only one or the other option is selected, only the first IF logic is being checked, (in this case Storage) and is successful in creating the Storage sub-task. If I select Compute, then the status in the audit log is "no actions performed."

What am I doing wrong? Any ideas? Thanks in advance for reviewing my question.

[Bill Sheboy · Accepted solution]

Hi @Durell Demartini 

Your rule is stopping processing because of the way the if-conditions are noted.  When you want processing to continue, please try using if/else conditions or branches.  Such as:

• trigger: your selected trigger
• if/else
  • condition: if contains the Storage value
    • action: create the sub-task desired
• with a new if/else
  • condition: if contains the Compute value
    • action: create the sub-task desired

Or try with branches

• trigger: your selected trigger
• branch on current issue
  • condition: if contains the Storage value
    • action: create the sub-task desired
• branch on current issue
  • condition: if contains the Compute value
    • action: create the sub-task desired

Kind regards,
Bill

[Dawid Joshua _TechTime_]

What @Bill Sheboy says. Let me just add a note or two. 

• Both conditions should be "contains any of". 
• Instead of the action "Create issue", you could use "Create sub-task". 
• As Sub-tasks can't be created for Epic-level issues, add a condition to exclude Epics. This will prevent errors. you don't need this if you already filter them out in your trigger step.
  
  
  

Cheers,
Dawid

[Durell Demartini]

Thanks very much for the quick replies and helpful information. @Bill Sheboy I failed to include that I had already tried if/else with no success. However, I hadn't tried the branching, so I did try that option, and it worked. Thanks again!