Combining Automations

Holly Hammond

I have two automations that work independently.  When they are both turned on, they don't work. My ultimate goal is to combine them, but I can't wrap my head around how.

My first automation is as follows:  When an issue is created and issue type equals story then create 3 subtasks (and I name them).  I have tested this several times.  When I create an issue (story) 3 subtasks are created.

My second automation is as follows: When an issue is created and issue is a subtask, defect, etc, then edit issue field (custom field)  I have also tested this and it works.  When I change the custom field in the parent issue, the custom field in the subtasks also change.

How do I combine these two?  So to recap.  I want subtasks to automatically be created when I create an issue (story) and when the custom field drop down is manually changed/added to the story, I need the same field in the subtasks to also be added. 

Any help is appreciated.

Thanks! 

 

 

 

Bill Sheboy

Hi @Holly Hammond -- Welcome to the Atlassian Community!

Short answer: although it might be possible to merge those rules, I recommend against some of what you describe. 

What problem you are are to solve by merging the rules?  That is, "why do this?"  Knowing that may help the community to offer other suggestions.  Until we know that...

 

You describe two scenarios, which could be combined using an if / else condition block:

WHEN an issue is created
AND the issue type equals Story
THEN create three Sub-tasks within the Story

WHEN an issue is created
AND the issue type is one of Sub-task, Defect, etc.
THEN edit "my custom field" to "some value"

 

Yet your second paragraph seems to indicate another rule:

GIVEN a Story
AND the Story has one or more child Sub-tasks
WHEN "my custom field" changes in the Story
THEN update the Sub-tasks' "my custom field" to match the parent Story

 

This one has a different triggering event than the first two rules.  Although it could be merged using the Multiple Issue Events trigger (recently renamed to Multiple Work Item Events), that would lead to problems:

1. There appear to be defects with that trigger and recent Jira changes such that the rule could run multiple times for the same issue change.  That would be bad for your scenarios.
2. Even though the "issue-updated" event can be detected, the changelog would not indicate which field changed.  As a result, your "my custom field" would be updated every single time there is a change to the issue...even for other field changes!

 

Kind regards,
Bill