Ensure Child Issue Due Dates Do Not Exceed Epic's Due Date
Asked by ???:

How Can I Create an automation rule with the coditions below?

### Rule Execution Trigger: {#toc-hId--2125413872}

* The rule should trigger **when an issue is updated**.

### Conditions: {#toc-hId-362098961}

1. **The parent issue** must be an **Epic**.
2. **The Epic issue** must have a **Due Date**.
3. **The Due Date** of the current issue (the trigger issue) **exceeds the Due Date of the Epic issue**.

### Action: {#toc-hId--1445355502}

* If the above conditions are met, **update the Due Date of the current issue (the trigger issue) to match the Due Date of the Epic issue**.


Answers:
author: Trudy Claspill
body: Hello [@???](/t5/user/viewprofilepage/user-id/4872621)

Welcome to the Atlassian community.

Have you tried to create this rule? Which elements are you unable to figure out? Please show us what you have so far.

comments: author: ???
body: I have already checked if the parent issue exists using a branch.

I proceeded with the conditions "within the same branch, the issue type is Epic, and the Epic's due date is not empty."

Next, I want to add an "and condition" to compare the due dates between the issue and the Epic, but since the `epic.duedate` smart value is no longer available, I am unsure how to proceed.


author: Trudy Claspill
body: Can you provide screen images show the rule you have constructed so far, in English?

Otherwise can you describe each step in the rule?

You mentioned in your reply that you are using a branch, but a branch should not be necessary. You can use Smart Value conditions to look at the information in the trigger issue's parent Epic.

![Screenshot 2024-09-05 at 1.52.08?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/345869iC217F0B2F674F35E/image-size/large?v=v2&px=999 "Screenshot 2024-09-05 at 1.52.08?PM.png")


author: ???
body: ![jira_automation.JPG](https://community.atlassian.com/t5/image/serverpage/image-id/346199i092354EACAD0153F/image-size/large?v=v2&px=999 "jira_automation.JPG")

This doesn't work.

Here are the steps of the rule:

Start condition: When the 'Due date' of an issue is edited

Condition 1: The issue's parent issue type is Epic  
Condition 2: The due date of the triggered issue is later than the due date of the parent issue (Epic)

Result: Change the due date of the triggered issue to match the due date of the Epic.


author: Trudy Claspill
body: Hello [@???](/t5/user/viewprofilepage/user-id/4872621)

Thank you for providing that additional information.

In what way exactly does the rule not work? What does the rule execution audit log tell you?

I see multiple problems with the rule you have shown.

1. The condition where you are checking if the issue type is Epic is being applied to the trigger issue, not the parent of the trigger issue.

2. The step where you compare the due date values of the trigger issue and its parent issue has errors in both of the smart values you used.

{{issue.due**t** ate}} needs to be {{issuedue**d**ate}}

{{issue.parent.d**ud** ate}} needs to be {{issue.parent.d**ued**ate}}

You might want to try using the rule I provided to see if that produces the result that you want.


Tags: cloud

jira-cloud