@Bill Sheboy not sure why I had to redo this. Regarding the previous question on automation (original question is below to trigger memory if needed)
The problem I am trying to solve by merging the rules is they don't seem to work when the two separate rules are turned on at the same time. They work individually. So i thought that combining them would be best, turns out that isn't so great either.
Basically our custom field has to (a policy) be filled out and using automation to copy the subtasks once the parent is manually selected is the easiest way to avoid forgetfulness. (2nd automation)
In addition those subtasks need to be automatically generated upon creation of the issue type story. (1st automation)
So what I am gathering here is combining them, not so great and I should avoid. But then why don't they work when they are both turned on?
Original Question:
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.
