Using Jira Automation, I want to set the due date of an epic and then automatically create sub-tasks

[진영 이]

How can I set up a Jira Automation rule to create sub-tasks in reverse chronological order, with due dates calculated backward from the epic's due date?

I'd like to explain the use case for the Automation I want to inquire about.

1. I plan to use it for backward scheduling of the project.

2. Each epic has a different nature. For example, Epic A might be about system development, while Epic B might be about content development.

3. Because of the different development tasks, both Epic A and B need to generate different sub-tasks.

4. Sub-tasks dependent on an epic should have different man-days. For instance, the sequence could be: brainstorming (3 days), idea sketching (1 day), system planning (5 days), and implementation (5 days).

[John Funk]

Hi @진영 이  - Welcome to the Atlassian Community!

Do you have an automation rule that you have already created and need assistance with? 

[Jack Brickey]

hi @진영 이 , you mention sub-tasks but I am guessing you mean tasks since tasks are children of epics. Regarding the fact that you wish to calculate due dates on the tasks dependent on the 'type' of epic you might consider using the labels field or a custom field to differentiate your epics. In this way your automation can use this in an if/else condition to create the tasks and calculate the due dates.

if you need assistance with the details of your automation I recommend starting by searching the community as there are quite a few posts dealing with how to create tasks under a new epic and how to calculate due date relative to the parent.