Auto-set Child Issue Due Dates X Days Before Epic Due Date

[Robert Kornel]

How can I use Jira automation to set or update child issue due dates to always be a set number of days before the epic’s due date? 

[Vitalii Rybka]

Hi @Robert Kornel,

To automatically set child issue due dates based on Epic due dates, you'll need a rule that triggers when Epic due dates change or when issues are linked to Epics.

Here's a basic approach:

Trigger: Issue updated (when due date changes on Epic) OR Issue linked (when child added to Epic)

Condition: Issue type = Epic OR Parent issue type = Epic

Action: Edit issues

• JQL: "Epic Link" = {{issue.key}} (for Epics) or use parent relationship for other hierarchies
• Set Due Date: {{issue.parent.duedate.minusDays(X)}} where X is your desired number of days

Smart values to consider:

• {{issue.parent.duedate.minusDays(5)}} - sets child 5 days before Epic
• Add null checks: {{#if issue.parent.duedate}}{{issue.parent.duedate.minusDays(5)}}{{/}}

Pro tip: You might need separate rules for:

1. When Epic due date changes (update all children)
2. When new issues are added to Epic (set initial due date)
3. Handling cases where Epic has no due date

@Bill Sheboy's suggestion about experimentation is spot-on. Start with a simple version and iterate based on your specific workflow needs.

What project type are you working with? The exact implementation can vary between company-managed and team-managed projects.

If you get stuck with the rule setup, feel free to DM me happy to help troubleshoot!

Hope this helps!

[Robert Kornel]

Thanks for the support. I was able to implement the automation by adding a branch for child items.

[Robert Kornel]

Hey @Vitalii Rybka @Bill Sheboy , do you know if it's possible to avoid applying the same due date to all child work items? Some should have an earlier due date than others. For context, I'm an event manager and we've recently migrated from Asana to Jira for project management. I'm trying to replicate our workflow. The Epic due date serves as the event date, and all child items are tasks that need to be completed before that date, but obviously not all on the same day.

[Bill Sheboy]

Hi @Robert Kornel -- Welcome to the Atlassian Community!

What have you tried thus far to solve this need?

If you have an automation rule which is not working as expected, please note context is important for the community to help.  Please post the following:

• what version of Jira are you using: Cloud, Server, or Data Center
• for Cloud, what type of project is this: company-managed, team-managed, JPD, etc.
• an image of your complete automation rule in a single image for continuity
• images of any relevant actions / conditions / branches
• an image of the audit log details showing the rule execution
• explain what is not working as expected and why you believe that to be the case

If you have not started a rule yet, I encourage you to identify when you want to update the fields and then to try to create the rules.  Several different rules may be required depending upon when you want the field updated, and all could use similar logic to calculate the date.

Successfully using automation rules requires learning and experimentation.  To get you started, please see these sources:

• https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/
• https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/
• https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Edit-issue
• https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/

Kind regards,
Bill