I want to create an automation that does the following 1. Create Epic 1 with parent link as Initiative 1 * Task with Epic 1 as parent 2. Create Epic 2 with parent link as Initiative 1 * Task with Epic 2 as parent 3. Create Epic 3 with parent link as Initiative 1 * Task with Epic 3 as parent I already know how to make the Epics & correctly link them to the initiative by using: { "fields": { "Parent Link": "{{triggerissue.key}}" } } How can I make the Tasks have their Epic Links be as defined above?

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How can I create multiple epics each with their own tasks associated in one rule?

Julia_a614zw

I want to create an automation that does the following

1. Create Epic 1 with parent link as Initiative 1

Task with Epic 1 as parent

2. Create Epic 2 with parent link as Initiative 1

Task with Epic 2 as parent

3. Create Epic 3 with parent link as Initiative 1

Task with Epic 3 as parent

I already know how to make the Epics & correctly link them to the initiative by using:

{
"fields": {
"Parent Link": "{{triggerissue.key}}"
}
}

How can I make the Tasks have their Epic Links be as defined above?

Accepted answers

Julia_a614zw

I ended up creating three rules. One to create the 2 epics and the following two to make tasks for each of those epics.

All comments

Mykenna Cepek

Just create the first Epic, and save that issue off in a variable from the {{createdIssue}} smart value:

https://support.atlassian.com/jira-software-cloud/docs/smart-values-general/#Smartvaluesgeneral---createdIssue--

Then create the first Task under that Epic, and use the saved variable to set the "Epic Link" field. This can be done in the GUI, no JSON needed.

Rinse and repeat!

Bill Sheboy

Hi @Mykenna Cepek and @Julia

I think that when you add the task, you can just set the "Epic Link" to {{createdIssue.key}} without the created variable, as that will contain the last created one in the rule...as long as it wasn't inside of a branch.

Kind regards,
Bill

Julia_a614zw

@Mykenna Cepek When you say "save that issue off in a variable" how can I do that? I know how to call {{createdissue}} but how do I do that for each epic and save them uniquely?

@[deleted]would that solution confuse the automation since the last created issue for some of the tasks would be a preceding task?

for example:

Epic 1:

Task 1 with epic link as {{createdIssue.key}} would work fine
Task 2 with epic link as {{CreatedIssue.key}} would the automation try to use Task 1 since it was created the most recently ?

Mykenna Cepek

@Julia You're concern about the last created issue being replaced by the most recently created Task is valid. This is why I suggested saving it in a variable.

To create a variable, just use the "Create Variable" action:

https://support.atlassian.com/jira-software-cloud/docs/automation-actions/#Automationactions-Createvariable

Basically you just make up a variable name (like "LatestEpic") and fill in {{createdIssue}} for the Smart Value. That variable will hold the value you set.

Then use {{LatestEpic}} when setting the "Epic Link" field for each new Task.

Once you've processed the first Epic and all it's Tasks, then create the second Epic, and use that same "Create Variable" action again (with identical parameters). This will update the variable to relate to the second Epic.

And so on!

Julia_a614zw

I ended up creating three rules. One to create the 2 epics and the following two to make tasks for each of those epics.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

automation