Help with automation on linked subtasks

[Julian Beardman]

Hello, 

I am trying to build an automation that will automatically update the start and due dates of linked issues from the trigger ticket. 

So far I have the linked issues updating fine but the linked issues have subtasks and i would also want their dates to be updated at the same time. I have tried many things, but cant get it to work. Does anyone have an idea on how I could do this?

Current setup of rule:

[Bill Sheboy · Accepted solution]

Hi @Julian Beardman -- Welcome to the Atlassian Community!

First thing:

Scenarios like this are quite challenging for automation because of the possibility of errors or missing some cases.  And when implemented incorrectly, they can cause runaway rule execution and halt all automation processing.

And so, what problem are you trying to solve by syncing the date fields?  That is, "why do this?"  Knowing that may help the community to suggest alternatives.

Next, the rule image you show is triggered on Issue Updated, and so that will run for all changes.  Is that what you wanted?  If instead you want the rule to only run when the Start Date or Due Date change, consider changing the trigger to check for changes to only those fields.

Next, when trying to update multiple issue levels / links, normally that cannot be easily done with one rule.  And when a second rule is used (just to update the subtasks) that could lead to runaway rule triggering for unrelated issues because this option must be enabled: "Check to allow other rule actions to trigger this rule..."

If you are setting all of the Start Dates to the same value (and the same thing for the Due Dates), one possible workaround to prevent problems is:

• gather the issue keys for all of the issues to update, using the Lookup Issues action and dynamic JQL expression
• then use a branch on JQL to iterate over them

This approach will only work when there are 100 issues or less to update.

Kind regards,
Bill

[Julian Beardman]

Hey Bill, 

Thanks for the reply! 

Im doing this as I have a go/no go task (A3PL-305) that if we say "no go" the next time we will review will be the following week, so the idea is that this rule will run on a schedule and if the due date is elapsed it will auto move the ticket to the next 7 days, and by doing this it will update all the corresponding linked tickets (and hopefully subtasks of the linked tickets) to add 7 days to their Start date and Due Date.

I was thinking of having another rule setup that is hard coded to the linked tickets and when they are updated it has a branch to update the subtasks as well but couldn't get that to work. 

Open to other ideas to make this happen

[Bill Sheboy]

I recommend against hardcoding as that could lead to maintenance and other errors.

Please try that last approach I suggested as it will allow the updates to happen within one rule, reducing the chance of errors.

[Julian Beardman]

So are you saying do something this this?

[Bill Sheboy]

No; my suggestion was to use Lookup Issues and JQL in place of the original branch on linked issues.  With that result, their subtasks may be found for each issue.  Then combine those key lists into a single list of keys which may be searched with a JQL branch to finally update the date fields.

If I have misunderstood your original question, perhaps try adding more details to the question.

[Julian Beardman]

Thanks, seems to be doing most of what i need!