Advanced Automation configuration rule

[Ted]

Is it possible to build an automation rule that will generate the following for me:

• Epic
  • Task
  • Task
  • Task
    • Subtask
    • Subtask
  • Task
    • Subtask
  • Task
    • Subtask

etc.

I'm trying to set up a project for one of our teams where they have a pre-determined workflow. This work management workflow includes the same tasks and subtasks every time they create a new epic. 

The use case is that I would like to be able to create an epic in this project, and at that moment get the entire list of tasks/subtasks to be automatically generated. These tasks and subtasks all have specific names and preferably would also then immediately have certain assignees. 

An additional consideration would be to not generate the entire list of tasks/subtasks upon creation of Epic, but to set up the automation so that the tasks only appear for the relevant step as the Epic moves through the workflow. 

I've been able to create an automation which will create a list of child issues which are linked to the epic via {{triggerissue}} , but I'm unable to also configure that some of these child issues should also have subtasks - this seems to be beyond what is configurable in Jira. 

Having these subtasks is pretty crucial to the team as the workflow is complex and touches on multiple teams, and they can't do without them. I'm a bit stuck as to what to do. 

Is another option to set up a "template" Epic which would have all of the tasks/subtasks created, at which point I could just ask the PO to clone that Epic when they want to create another one, at which point they will have the whole workflow without having to create it manually. 

But as far as I can tell, bulk cloning like this is not supported by Jira out of the box either...

Any help here is much appreciated! 

[Trudy Claspill · Accepted solution]

Hello @Ted 

Yes, the creation of tasks and subtasks can be done in an automation rule.

In the rule triggered by the creation of the Epic (or the change of Epic status) after the trigger:

Action: Create issue (create a Task)
|-- For Each: Related Issue: Most Recently Created Issue
    |-- Action: Create Sub-task (create the subtasks for the recently created issue

Repeat the above structure in your rule for each Task you want to create with subtasks below.

[Ted]

Hi @Trudy Claspill 

Brilliant, that's the solution! Thank you for your help, saved me a massive headache :)