Automation for Jira-NextGen-Create set of tasks when epic is created & have trigger epic as parent

[Ibrahim Al-Taie]

Hi,
I want to: whenever an epic is created in a specific jira project (NextGen), a set of tasks are created, with the trigger epic as their parent

since it's a NextGen jira project, using "epic link" or "epic name" doesn't work.

and Parent doesn't exist in the list of fields that we can use from "Choose fields to set" list.

I tried the additional fields but all my the options I've used didn't seem to work.

any advice or suggestions are welcome

[Ibrahim Al-Taie · Accepted solution]

I found a way to get it to work, @Melissa Foley @Angélica Luz @[deleted] 

The issue was that the "parent" was expecting an json object, not a string. and once I figured that out, i understood that we can pair the "key" of the parent of this ticket, to the trigger issue key

In the "More options" => "Additional fields", paste the following within the created ticket

{
"fields": {
"parent": {"key": "{{issue.key}}"}
}
}

[Angélica Luz]

Hello Ibrahim,

Welcome to Atlassian Community!

Searching using the details you provided, I didn't find any information on how to create subtasks for an Epic using automation and I also tested on my local site and I'm afraid there is no such option. 

The workaround would be to use scriptrunner or power scripts as mentioned on the threads below:

•  How to automatically create a issues when a epic jira is created
•  How to create a issue (sub task)when Epic is create (Scriptrunner)

Both add-ons you can try for free:

• ScriptRunner for Jira
• Power Scripts™ - Jira script automation

Regards,
Angélica

[Ibrahim Al-Taie]

Thank you @Angélica Luz for the response!

what I want to create is Tasks not Sub-tasks

furthermore, it seems like an issue within Jira NextGen, that the "Parent" field is not recognized as a field that can be set to specific information, or the documentation doesn't reflect the correct data at least.

I know this can be done within a classic Jira project, but some of the features in the NextGen are important for the project I'm working on.

scriptRunner or Power Scripts won't do the trick, because the issue still remains: Having access to information of how to edit the parent field (without doing this in the created issue UI).

[Melissa Foley]

Did you ever get this to work? I'm having the same issue.

[Ibrahim Al-Taie]

@Melissa Foley 

unfortunately, not

the work-around I implemented is 

create a field names "parent name", which gets the {{trigger.issue.key}} populated (so that data is not lost)

than manually add those tickets to the parent/epic.