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; } } }

I want to use Jira automation to create a child issue of a child issue

koutarou ishibashi

Create a child issue by filling in the following additional fields
{
"fields": {
"Parent Link" : "{{issue.parent.key}}"
}
}

I want to create a child issue of the created issue.
I want to implement it with one automation
Please lend us your wisdom on how to implement

Accepted answers

All comments

Michel Neeser

Hi @koutarou ishibashi

I think you can achieve your goal with an automation rule like this:

koutarou ishibashi

Thank you for your answer. because of the special environment it cannot be created that way

As you can see in the image, we have created a new issue and created a child issue of the parent parent with "Parent Link" : "{{issue.parent.parent.key}}".

I want to create a child in the issue I created

Marc -Devoteam-

Hi @koutarou ishibashi

You cloud try the following.

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

But I'm not sure as I see your rule.

Can you explain in English what all steps are in the current rule?

koutarou ishibashi

I'm setting up a custom hierarchy.

There are three hierarchy levels: 3, 2, and 1

The parent of 1 is 2 and the parent of 2 is 3

Trigger manually at hierarchy level 1

Custom Fields_10228 is of type Select List (multiple choices).

Repeat the same process for as many as the value of Custom Fields

Create a tier 2 Epic below
"Parent Link" : "{{issue.parent.parent.key}}"

I want to create a story that is a subordinate of the Epic I created.

(I want you to tell me how to do it here)

Michel Neeser

@koutarou ishibashi You have to differentiate between sub tasks and child tasks. The parent/child relationship you're referring to applies to sub tasks. But it seems that you want to create a child task below an epic task. So you have to specify the epic link like this:

Marc -Devoteam-

Hi @koutarou ishibashi

I don't think this is going to work in the same rule.

As the Story you are creating doesn't know the Epic that is created.

Add an action to re-fetch data

You could look at making 2 log actions between action to create the Epic and the action to create the Story.

Is their information in the log action, you would need to log the information on the issue key and Epic Link.

Then if there is information you should create a variable to log this and use the variable on setting the Epic Link value in the Story

But as I said I don't know if this will work.

Welcome!

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

Quick Links

Find more posts tagged with

confluence

cloud

confluence-cloud