Can I create separate child task rules for automations?

Question

I have created an automation rule for created issues:

* When issue created
* Create 7 sub-tasks 
* Condition: When the description contains design elements.

I want to create another similar one with a different set of sub-tasks and a different description condition. This one adds sub-tasks from both rules regardless of what is typed into the description.

Is there a way around this?

Mikael Sandberg · Answer

My guess without seeing the descriptions for both would be that they both contain "Design elements" and "Analysis" in the description field and that is why you get all 10 subtasks.

When using the contains condition, especially on multiline fields you have to be very specific in what you are looking for, since if you are just looking for one of two words the probability that those words are in the fields goes up.

Hazel Edmends · Answer

Hey Mikeal, I appreciate you responding so quickly. I tried the first option, copied the rule, and added different if/else conditions based on the descriptions. I created 7 sub-tasks in one rule and 3 for the other rule.

However, no matter which description I add, it pulls all 10 sub-tasks when I create a new issue.

Any clues where I went wrong?

My If/else conditions were: 
First rule: to create 7 specified sub-tasks

Field: description

Condition: contains

Value: Design elements

Second rule: to create 3 specified sub-tasks

My If/else conditions were: 
Field: description

Condition: contains

Value: Analysis

Mikael Sandberg · Answer

Hi @Hazel Edmends,

Welcome to Atlassian Community!

You have a couple of options, one is to copy the rule that you have and then just make the changes needed for it. Another option is to utilize the if/else condition and base that on the description.

A third option would be to use a dispatcher, basically what it does is using if/else conditions to determine which automation it should call using web request and incoming web request.

I use the dispatch option most of the time, since it is scalable and you can go in and quickly disable a condition if needed.