Update dates based on dependencies

[Katie Joskowitz]

A = original blocking issue

B = blocked by A

C = blocked by B

I set up an automation so that the start/end dates of a dependent issue (B) are updated when the actual completion date of the blocking issue (A) is updated. However, when I run the automation, the issue immediately linked to the blocker (B) updates, but none of the issues blocked by issue B update. Is there a way to ensure that when A is updated, it will change B and since B is being updated it will update C and so on?

[Shawn Doyle - ReleaseTEAM]

It looks like this automation runs when A changes, so the automation knows of A and can go through it's linked issues to update B.  It doesn't know of B's linked issues, so can not update them.

A few ways to approach this;

1. You would need this automation to load all of B's linked issues and update them, most likely in a branch. 

2. Create a separate automation for when B issues changes to update the linked issues.

3. Make the current automation trigger smarter to catch both A date changes OR B date changes to update their linked issues.