Automation - create an epic and tasks inside that epic

[Gema Ruiz]

Hi all, and thanks in advaced :)

I want to create a automation rule that every time a new project is created, the rule must creates an epic and some tasks inside that epic.

I am able to create the rule to create a new epic, but I cannot create the tasks inside the initial epic, I cannot find the way to relation tasks and epic, any idea/help, please?

Thank you very much

[Jack Brickey · Accepted solution]

Hi @Gema Ruiz , it would help to see an image of your automation rule so that we might explain how to add to it to create your final solution. In any event, you may also want to search the community as there are a lot of posts about creating Epics and tasks within that epic under automation. There are a number of ways to achieve this and I have presented a quick example below. The method below employees, the use of a variable to capture the epic key subset. It can be used when creating the stories where you need to define the Epic link.

[Gema Ruiz]

Hi, this is exactly what I want to do... the problem is, since this morning (in Spain) most of the fields has disspeared , and I cannot add it to the epic or task..., I have to use advance configuration, and I don´t know how to set the value to the epic link field:

This is wrong and no working:

[Gema Ruiz]

sorry, I was choosing the wrong type of issue.... sorry!

[Gema Ruiz]

@Jack Brickey , please, could you show me how do yo create the variable? thank you a lot!

[Gema Ruiz]

Hi again @Jack Brickey , please, could you show me how did you create the variable?

Thanks in advanced!

[Jack Brickey]

@Gema Ruiz , here is an example of a variable for the just created issue...

[Gema Ruiz]

Thank you very much!!

[Hauke Bruno Wollentin · Accepted solution]

In that same automation rule you can use a branch rule to run against the least created issue. This should do :) 

[Gema Ruiz]

I am not able to make it right...

I guess I have too many errors, coud you help me?

[Hauke Bruno Wollentin]

There is one closing bracket too much in your JSON but you do not need this at all I'd say.

You can use the Epic Link field like this:

The {{issue}} smart values relates to the branch issue.

[Gema Ruiz]

It works!!!

Thank you very very much!!!

[Gema Ruiz]

Hi again,

I have a question when I use this brach rule:

is working for all the projects, or only for the project in which I created the previous epic?

I mean, if for some reason, someone is creating an issue in other project at the same time that this rule is triggered, it will create my tasks inside his epic? or the branch only works for the most current issue created in the project I created the previous issue?

Thank you very much.

[Hauke Bruno Wollentin]

This works for other projects or cross-project too, but the automation rule need to be global than.

In a global rule this type of branch rule really picks the last created issue, no matter what project the rule triggering issue is in.