Creating tasks as child issues of epic issue - Automation

[Jakub Zděblo]

I would like to create Epic issue with predefined children task issues automatically. 

When Created Issue = Epic

Than Create Issues as children to the triggered issue:

Task1

Task2

Task3

Thank you for your help.

[Evaline Poetsema · Accepted solution]

I have the same problem. This automation does not contain a rule to place the issue as a child issue of an Epic in my Next Gen roadmap. The automated tasks just appear in the backlog. 

[Teja]

How to achieve this in Jira server using script runner (Issues in Epic)

[Jeremy Fischer]

So I have a slightly different issue with this.  I need to create an Epic and then create stories attached to the epic.  But instead of the trigger being to create an issue, we need to have the trigger be a schedule.  They are quarterly tasks that have to be done.

Any thoughts on this?

This last run, it created the Epic needed on the scheduled day/time.  And it created the tasks needed.  However, it didn't link the tasks to the created Epic.

Anyone know what I'm missing?

[David Hayward]

I have done something similar that I suspect might be the answer for you. I created an epic and an epic task on a manual trigger.

You can see I am creating an epic in one project and adding a task to the epic from a different project. I also send an email to the initiator to remind them to update the epic and child ticket. Hoping "Current Issue" resolves your problem in combination with the branch.

[Alex Wasserman]

I have an Epic created on a schedule and then use the branch - "Most Recently Created New Issue" to create Tasks within it, using the "Epic Link" and Trigger Issue.

However, what I can't do is then create sub-tasks under some of those Tasks.

Creating sub-tasks off the current or trigger all come under the Epic directly, rather than the most recent Task.

I can't nest another branch within that branch either, and trying it from the root just links back to the original Epic.

[Jack Brickey]

Hi Jakub,

here is an example of an automation I created for the same. i create multiple tasks and sub-tasks as well.

[Jakub Zděblo]

Thank you very much. But this example creates a task which doesn't belong to the epic I have just created. 

I would like to have task as a child to the epic.

[Joanna Boehme]

I have the same request, to create an epic and automatically create child issues

[Luki]

I do have the same problem. I was able to create issues when an epic was created but wasn't able to connect them to the newly created epic. Or any suggestion from your side @Jack Brickey ?

[Luki]

FinalIy I was able to solve this problem doing the following:

The outcome looks like this:

[Jakub Zděblo]

Hi @Luki

Great, it works perfectly. Thank you so much! 

[Evaline Poetsema]

@Luki Thank you so much! This is making my Nex Gen project super automated :D

[Kavitha Chikkam]

Can someone advise what is the "Trigger Issue" in the Epic Link..

[BrentBot_]

@Luki I have tried both of the above and i am still not getting a positive result. We use kanban only right now and have a hierarchy of :

initiative

epic

child issues

The child issues are issue types we created such as step 1, step 2 etc within our org's workflow. Bottom line, when i follow the above steps, no child issues are added, as if they are not even being made. I read some where that you need script runner for the cloud automation to work; is this true? do you guys all have script runner in your bundle as well to execute automation.

Thank you for any help; we are trying to vastly reduce our setup time for our projects

[BrentBot_]

nevermind! i figured it out!!

[Tatyana Fermon]

@BrentBot_  don't never mind - what did you figure out, please? :)

[Swati Thapliyal]

Even I tried the same but no results. Can any one explain what else to be done after setting up "Trigger Issue" in the Epic Link.