HOw to automatically create Task and Subtask for a created EPIC

Question

Dear all,

I am actually study the efficient and more proof way to create the following using automation.

* When an EPIC is created I need to create its equivalent Task list ( around 10 tasks)
* Then for each of those created tasks , I need to create a certain amount of sub task

I have run different test for doing this like :

* Create an Isssue Created trigger on an EPIC type to create all Tasks for the epic
* Manual triger on a Task which as EPCI as parent, to create sub tasks ( more than 10)

By doing so, I have notice that it can works the the automation rule can be really big depending on the number of task to create in addition to set predefined field for each of them

I have seen that REST api send request could be used in Automation.
Does that approach is capable to create in one shot the whole TASK and Sub Tasks structure linked to proper parent ?

Thanks for your experience

serge calderara · Answer

hello @Yong Yang ,

Each sepecifc time in calendar, this automation will create all time the same amount of task and sub-tasks for each task.

Today we rewrite them all each time we need to execute a new run.

Based on your question :

1- Each epic will have different number of Task but each task are cleary identified for each Epic with predefined summary and description

2- Each created Tasks will have same set of Subtask based on the Task summary with a define task prefix ID

I have done such with a simple one rule but it is a really huge set of action and trying to do it in a better way ( goal is in one rule execution, if no may be two rule execution which gest strt when rule 1 fully complete, or full Send request http action

regards

Yong Yang · Answer

Hi @serge calderara

What's business scenario of this requirement? I may want to know firstly before providing my suggstion:

1.what's the rule of epic child tasks creation? only the issue type of Epic, you will need the same set of tasks to be created?

2.what's the rule of sub-tasks creation? based on the parent task's summary with certain key words?

Thanks,

YY哥