Create an automation for Due date
Asked by DELACRUZ Guerdly _Gigi_:

Hello! I'm trying to create an automation to change the due date and the trigger would be a change on the start/ due date on one specifc issue

For example, i have an issue called "go live " that starts June 30th and the due date is July 25th.

If a change is made on the due date/ start date it will update ALL issues in that project base on the number of days updated

eg. old Start date= June 30/old due date= August 30 -\> change = +2days -\> new start date: July 2, new due date: August 2   

My other options could be that when an issue in an epic start date changes it updates all related issues

I had done a few smart values but it would remove the due date value when I would update the start date. :(

Thank you !


Answers:
author: Trudy Claspill
body: Hello [@DELACRUZ Guerdly _Gigi_](/t5/user/viewprofilepage/user-id/5531175)

Welcome to the Atlassian community.

Take a look at the answer I added to this post:

<https://community.atlassian.com/t5/Jira-questions/Change-due-date-of-story-issue-when-epic-due-date-changes-while/qaq-p/2722945>

I explain there how to calculate the change of duration when dates are changed, and then use that to update the date of another issues.

After reviewing that, let us know if you have additional questions about how to implement your requirement in automation rules.

comments: author: DELACRUZ Guerdly _Gigi_
body: Would it be possible to do it for all linked issues related to that epic?

For example, I changed the due date of the epic then all the children task in that epic will change. but I wanted to trigger also that related epic also change the due date which would trigger the change for their children tasks.

Do you see what what I mean ?   

![image (8).png](https://community.atlassian.com/t5/image/serverpage/image-id/332311i920BC756F9014CED/image-size/large?v=v2&px=999 "image (8).png")


author: DELACRUZ Guerdly _Gigi_
body: ure ! Thank you that would be great ! :)

![Screenshot 2024-06-28 084845.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/332313i763EDC72520214B9/image-size/large?v=v2&px=999 "Screenshot 2024-06-28 084845.jpg")

![image (9).png](https://community.atlassian.com/t5/image/serverpage/image-id/332314iF2F8149299AAFE56/image-size/large?v=v2&px=999 "image (9).png")


author: Trudy Claspill
body: Hello [@DELACRUZ Guerdly _Gigi_](/t5/user/viewprofilepage/user-id/5531175)

Yes, you can change the dates on both child issues and linked issues.

The structure you have appears to be correct for accomplishing that.

If you change the date on Epic 1, and that changes the date on Epic 2, then I assume you want the dates of the children of Epic 2 to also change. In that case you need to have this box checked on the Rule Details page.

![Screenshot 2024-06-28 at 8.03.16?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/332418i2EFD0D5723BBE0F8/image-size/large?v=v2&px=999 "Screenshot 2024-06-28 at 8.03.16?AM.png")

Do you want this rule to run only when the date on an Epic is changed? If so, you should add a condition after the Trigger to confirm that the Issue Type of the trigger issue is Epic. Otherwise this rule could be triggered for a date change on any issue type, and could then try to change the dates on other issue types that are linked issues.

For the change to linked issues, do you want to update only Epics that are linked to the changed issue? If so, you should add a condition in the Linked Issues branch also to confirm that the issue type of the linked issue is an Epic.


author: DELACRUZ Guerdly _Gigi_
body: Yes my plan would be to have an epic that is the end of the project , for example a go live epic. then if the due date on that issue is changed it would change all the epics and their child task


author: DELACRUZ Guerdly _Gigi_
body: thank you for all your help!


author: Trudy Claspill
body: You're welcome.

If my responses have helped you solve your requirement please consider clicking on the Answer Accepted button to mark your post as Solved.


Tags: cloud

jira-cloud