How to create loops in a Jira automation

Question

I need help with the following issue.

This is my automation:

* Trigger: Value Changes for Start date, Duration
* Then: Edit issue field Due Date (=Issue Start Date + Duration)
* And: Re-Fetch issue Data* Branch For Linked Issues, Types: Linked issue cannot start until this issue finishes
* Then: Edit issue field Start Date (=Linked issue DueDate+1day)
* And: Re-fetch issue data
* And: Edit Issue fields Due Date (=Issue Start Date + Duration)
* And: Re-fetch issue data

This is the problem:

* I manually update the Start date of HA11-2
* Then the Due date of HA11-2 get's updated. This is OK
* Then the Start date of HA11-3 gets updated. This is OK
* Then the Due date of HA11-3 gets updated. This is OK

Then it stops, but the rest of the issues are linked as well. I am expecting all linked issues to continue updating.

Alanis, Hans · Answer

@Jack Brickey , Thanks for your response. I saw @Trudy P Claspill 's comment and his suggestion fixed my problem. But now I have the other issue with needing this to execute to all my 180 issues.

Alanis, Hans · Answer

Thanks @Trudy P Claspill . Selecting that checkbox fixed the issue.
Now, to answer your questions.
Yes HA11-5 is linked to HA11-4 
HA11-4 is linked to HA11-3 
HA11-3 is linked to HA11-2....and so on.

I didn't know this type of trigger is limited to 10 execution. This will be a problem for me as I have 180 issues in my project, all linked as I mentioned above.
What I want to do is that if I change the Start Date of any of the issues, I want the chain of linked issues to be updated.

Is there a different way to achieve this?

Trudy P Claspill · Answer

Hello @Alanis, Hans

How are the issues linked? Is HA11-4 linked to HA11-2 or to HA11-3?

The rule you have written will change only the issues that are directly linked to the trigger issue - HA11-2.

If your issues are linked in a chain, then on the Rule Details page you need to check this box:

Then the update of HA11-3 will cause the rule to be triggered again for HA11-3 and update the issues linked to HA11-3, and so on through the chain of linked issues.

However this sort of trigger-itself action is limited to 10 such executions. If you have more than 10 issues in the chain additional actions have to be taken to address that.