Advanced Roadmap Dependency setup by Dates

[Spartans]

Give me any way to find a automation for this issue. Since this is used as a test purpose, Will be applying the automation in organization live set up.

Please provide a best solution for this ?

If the  [Story-1] of Due Date ≠ Start Date of [Story - 2]

It should change the date when the due date is increased.

Once your Due date changes to 10th, the start date should change one day ahead like 11th of Story-

[Trudy Claspill · Accepted solution]

Hello @Spartans 

If you use Advanced Roadmaps (available only with the Premium plan) you can use the Auto-schedule feature to automatically maintain the dates between dependent tasks. Refer to 

https://support.atlassian.com/jira-software-cloud/docs/auto-schedule-issues-on-your-advanced-roadmaps-timeline/

The problem with trying to manage this with an Automation Rule is that you would be setting up a recursive rule; the change to the first issue would trigger the rule, causing a change to the second issue. The change to the second issue would trigger the rule again, causing the change to the third issue, and so on. That recursive calling structure is limited to 10 calls. If you have more than 10 dependent issues that need to be changed, the rule would stop running after updating the 10th issue in the chain.

[Spartans]

Please then give me a idea for recursive rule so I will try that.

We tried the Auto-schedule option in Jira, but, we are not able to get a best option. So If I get a good option, then I would apply it in our work environment(i.e., on Advanced roadmap).

Also please explain the recursive method how it works and the automation rule on that for only the due --> start 

 

[Trudy Claspill]

The basic structure of the rule would be

TRIGGER: Field value changed
  Field to monitor: Due Date
ACTION: Create Variable
  Variable Name: dueDateDiff
  In this step you calculate the difference between the original Due date and the new Due date and assign that to a variable
BRANCH: For Related Issues / Linked Issues
  Link type: "blocks"
  |-- ACTION: Edit issue
        Field to edit: Start date
        Field to edit: Due date
          For both of the above you would set the field value using the fields original value plus the value you calculated for your Variable earlier

Lets say you have the following issue dependency chain:

AAA-1 blocks AAA-2 blocks AAA-3

When you change the Due date on AAA-1 the above rule will get triggered, with AAA-1 being the triggering issue.

In that execution of the rule, AAA-2 will get its Due date changed.

When the rule changes the Due date on AAA-2, that will cause the rule to be triggered again with AAA-2 being the triggering issue.

• In the execution of the rule triggered by AAA-2 being changed, AAA-3 will get its Due date changed.
• When the rule changes the Due date on AAA-3, that will cause the rule to be triggered again with AAA-3 being the trigger issue.
  • In the execution of the rule triggered by AAA-3 being changed, the branch to find linked issues will find nothing. The rule will not be triggered again.

That is an example of a recursive rule - the rule causes some change and that change causes the rule to be executed again for a different issue.

If you change an issue Due date where there is a chain of 10 or more issues that subsequently have to be changed, only the first 10 issues would be updated. Any issues after that in the chain would not be updated.