Can Automations be used to generate a standard set of tasks and sub-tasks?

[Si Walker]

I am trying to automate the generation of a standard set of tasks and sub-tasks that will run once a new Epic is created in Jira Cloud. Is that possible without adding a marketplace app?

I have created an Automation but when it runs, the Tasks are not nested under the Epic and none of the Sub-Tasks are created either.

[Ponnappan Ganapathiya]

https://community.atlassian.com/t5/Jira-questions/Automation-to-Create-Task-and-Sub-Task-under-it-when-Epic-is/qaq-p/2742400 

You can take a look at this.

[Dick]

Hi @Si Walker , welcome to the Atlassian Community!

Yes, automations can generate fully filled tasks and sub-tasks for you, when an epic is created. You wouldn't need a marketplace app. 

You can "nest' tasks under an epic by setting the epic link field to the newly created epic key. 

Hope this helps,

Dick

[Si Walker]

Thanks @Ponnappan Ganapathiya  and @Dick 

Here's how I currently have it set up which creates a Task and each of their sub-tasks but it isn't created within the newly created Epic. Any ideas?

[Ponnappan Ganapathiya]

I am sorry, You want to link the task with epic?

[Ponnappan Ganapathiya]

Did you try this?

While creating task edit the Epic link field.

[Si Walker]

Thanks, really appreciate your help and advice.

We use Jira Cloud more like a project management tool so on each Jira software project board (we have several) there may be 100+ Epics but each of these Epics needs to have an identical set of tasks and sub-tasks.

A User will create an Epic and give it a specific, unique title. What I want the automation to do is trigger when the Epic is created and automatically populate it with the tasks and sub-tasks.

At the moment, the automation triggers when the Epic is created but it doesn't populate that Epic with all the tasks. The tasks it does create do not have a Parent.

Does that make sense.

[Ponnappan Ganapathiya]

@Si Walker 

From your reply, I understand the task is created but not linked with the Epic!!!

https://confluence.atlassian.com/jirakb/epic-name-vs-epic-link-779158632.html

This epic link field connects between Task and Epics. If you add this field to Task create screen you can set the value as trigger issue, which is the Epic that trigger that rule. Hope this should work.