Automation Rule for creating and updating multiple tasks (children associated with epic/parent)

[Sabrina Mösenbacher]

Hello Atlassian community.

I have a problem with an automation rule (Jira Cloud) that works the first time I run it, but creates unwanted duplicate entries when I run it again.

My use case is as follows:
I want the rule to create a overall timeline based on multiple tasks, starting with my “custom estimated date”. Since this is an initial estimated date, the rule needs to be able to adjust the affected date fields for the existing tasks (children) when it is re-executed.
The start date and due date of the children should be adjusted as follows via smartvalue usage -> {{triggerIssue.°custom estimate date.plusBusinessDays(X)}}.

Of course, a different number of BusinessDays must be updated for each task (based on the initially created task)

Please help - it just won't work. I am open to all suggestions for solutions - thank you very much in advance.

[John Funk]

Hi Sabrina - Welcome to the Atlassian Community!

Can you share the rule that you have so far? 

[Sabrina Mösenbacher]

Hello John,
thanks for the quick response.

Here is a screenshot of my automation rule so far.
Thanks in advance.

[John Funk]

Sorry, this is really small and hard to see. Maybe capture in 3 different sections so the image is larger. 

What is the trigger? How does X get updated? 

[Sabrina Mösenbacher]

Here the rule is split into three screenshots.

As a rule trigger I used my custom field “estimated order date”, if a change occurs here (create, update, etc.), the rule is triggered.

Then I try to either create the task using branching or update the task with new date if available. Apparently it is not possible to use the if/else block within a branch - I would find that very useful here. But hence the current attempt at a solution.

As for the update part, if the child already exists, only the start date and due date fields of that child should be updated. Here I currently use this smart value variant:

{{triggerIssue.°Estimated order date.plusBusinessDays(number of days required)}}

[John Funk]

Just a quick response - but I tend to create multi branches For Current Issue to handle the lack of IF/ELSE available under the branch. 

[Sabrina Mösenbacher]

Hello John. I have created several branches for the current issue. What would your solution to my use case look like? Or do you use advanced branching?

[John Funk]

Can you share what you have? Is it working? 

[Sabrina Mösenbacher]

I have already shared my automation rule. And yes, it works initially, then when I want to change the date again, I get task duplicates.

[John Funk]

I suggested multiple branches based on Current issue. Did you not do that?