How to create automation rule to change the start date and due date of all linked issues under Epic?

[Jasmeen Bajracharya]

Automation rule is working for only one linked issue and not the nested linked issue.

that is if there are 4 linked issues t1,t2,t3,t4, then changing due date of t1 then t2 start and due date is changed by automation while t3, t4 are not changed.

[GNarsimhagowda - Empyra]

Hi @Jasmeen Bajracharya  

The way you were trying to acheive keeps triggering the rule and keeps running as KP-18 is linked with KP-17 but however i have created an automation that is working for me and it updated the last linked issue and did not repeat itself here is the screenshot of the automation that worked for me

Thanks;

[Bill Sheboy]

Hi @Jasmeen Bajracharya 

What you describe may be possible, but it is risky for an automation rule to process this.

You describe updating the Start Date and Due Date for linked issues, in a chain of issues.  This is similar to what a project management tool could do.  For example: 

KP-15 links to -> KP-16 links to -> KP-17 links to -> KP-18

Your rule is only changing the issues linked to the first, trigger issue.  The reason is, by default, the actions of a rule cannot trigger other rules (or the same rule).  This is to prevent looping and errors, and serious performance problems in rule execution.

When one intentionally wants a rule to trigger others, the "downstream rule" to be triggered should enable the "Allow Rule Trigger" option in the rule details.  For your scenario, that would mean enabling the option for this rule, essentially making it recursive.

Now for the risky parts:

• Your rule is using a branch on linked issues.  Branches like that are run in parallel and asynchronously.  There is no guarantee of when the branch will finish, up to the last step of the rule.
• When a rule triggers other rules using the "Allow Rule Trigger" option, there is a service limit of 10 executions in "quick succession before the execution is stopped and marked as a LOOP": https://support.atlassian.com/cloud-automation/docs/automation-service-limits/

For your scenario, if there are ever more than 10 issues in a link chain, or any cross-linked issues (intentionally or accidentally), that single rule will halt.  It may also lead to other service limit breaches, and halt execution of all rules in your site.

Kind regards,
Bill

[Geethanjali Katagani]

Hi @Jasmeen Bajracharya ,

To facilitate the automatic update of linked issues under an epic when the epic's due date changes, I have implemented the following automation:

Let me know if you have any questions or if further clarification is needed.

Thanks,

Geethanjali

[GNarsimhagowda - Empyra]

Hi, @Jasmeen Bajracharya 

Try changing the Branch from linked issues type : blocks to All link types.

Thanks

[Jasmeen Bajracharya]

hi @GNarsimhagowda - Empyra,

 Thanks for the prompt reply but though Blocks changed to all Link types, it is not changing the nested link issue,

Before changing is as below

After changing the due date of KP-15

as shown in above , Changing KP-15 due date from 6th dec to 7th dec, the start and due date of KP-16 only changed but KP-17 and KP-18 are not changed.

[GNarsimhagowda - Empyra]

Hi @Jasmeen Bajracharya 

I got to know the problem for this since KP-15 triggered the automation it has checked for the linked issues in that issue and has updated the due date. if i am right KP-15 is linked only with KP-16 so it has changed its value only. 

[Jasmeen Bajracharya]

Yes, KP-15 is linked with KP-16. KP-16 linked with KP-17, KP-17 linked with KP-18.

How can automation for that be achieved so that all linked issues start date and due date will be updated at once?

[Brandon Monahan]

Did you ever get an answer or find a solution?