Rule automation - creating child issues

[Dorothy Callahan]

Hi all,

We have some epics, when created to a specific component, will always have the same child issues.  I was hoping to create automation rule when an epic is created to this specific component then create defined child issues.  It would behave in the same manner as the "Create Sub-tasks" template but instead when issue created issue type Epic create child issues completing summary and fields.

Thanks

[Jack Brickey]

Hi @Dorothy Callahan ,

do you have a rule that you are working on that is falling short? Based on what you have stated here it should be pretty straightforward to edit the template. It seems like the only thing you need is to check if the issue type is an epic, and if a certain component is set. Then you simply create your child issues and edit the necessary values to meet your needs. it might be easier for me to provide feedback if I had a starting point rule to work from.

[Dorothy Callahan]

Attached is what the sub-task automation looks like.  Problem would be solved if it allowed a drop down to choose "child issues" versus "sub-tasks".

[Jack Brickey]

So it seems you just want this or similar? Please let me know if I am missing something.

[Dorothy Callahan]

Hi,

Embarrassingly, copy from trigger issue seems to be the part I was missing.  It's easier to create sub-tasks than story but this definitely works.

Thanks so much.  

[Jack Brickey]

Cool. Please considering accepting the answer.

[Dorothy Callahan]

I apologize.  I was out of office and was told this worked but it did not.  Ultimately, all I need is to create child issues stories when an epic is created and summary contains "New Client".  The above recommendation did create stories but did not populate Epic Link in these stories and therefore do not appear as child issues.

[Colleen Gotling]

I am looking to do the same thing.  When I try to populate the "epic link" during automation, it doesn't allow me to use a smart value or a dynamic value.  

[Dorothy Callahan]

Hi Colleen,

This is my convoluted work around below in case this helps.

Create an automation action when creating epic and condition epic name is "new client"

Add actions "create issue".  Then I added an "create issue" for every story needed under that condition.

I create a "new client" epic

It automates stories

Then I do a bulk edit to link all stories to my "true" epic using filter > Project = (your project) and reporter = "automation for Jira" (should be available as a reporter) and epic link is empty

Then delete the New Client epic

It stinks but after you do it a couple of times it takes seconds.  I will watch for any other suggestions though!

[Majken Longlade]

So I know this is late, but for anyone who's looking to do the same thing, instead of "Copy from trigger issue" the value for Epic Link should be the smart value {{triggerIssue}}

Copy from trigger issue means look at the Epic Link field for the trigger issue, which is invalid for Epics. You want to use the trigger issue itself as the Epic Link.

Just found a relevant kb article https://confluence.atlassian.com/automationkb/jira-automation-create-and-link-child-issues-with-epic-when-rule-triggered-manually-from-an-existing-epic-1188419965.html