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

Automate Epic -> Multiple stories creation

Rachana Kandlagunta

Hi-

I’m looking for help here please-

I need to automate Epic and create multiple (4) stories linked to the same Epic.

I’m using smart value for the 1st story {createdissue) at the Parent field and works as expected.

when I set the same for stories 2-4 nothing works

please suggest @Bill Sheboy

Thank you

Accepted answers

Bill Sheboy

Hi @Rachana Kandlagunta -- Welcome to the Atlassian Community!

For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas. Thanks!

Until we see those...

From what you describe, I suspect your rule looks like this:

trigger: some trigger
action: create issue, for the epic
action: create issue, for a story, setting the parent to {{createdIssue.key}}
action: create issue, for a story, setting the parent to {{createdIssue.key}}
...

When using this structure, {{createdIssue}} is changing as you add each issue. When you instead want to use the same issue as the parent, two solutions approaches are:

After creating the epic, branch to Most Recently Created Issue, and change the sets of the parent field to be the current issue or {{issue.key}} as that will refer to the branched-to issue: the epic
After creating the epic, save it's key in a created variable, and use that when setting the parent field for each issue

Kind regards,
Bill

All comments

Thuan_ Do Dang

Hi @Rachana Kandlagunta ,

Which issue triggered the Automation? Is this the Epic?

If that, you can choose "Trigger issue" in Parent field.

Hope this helps!

Bill Sheboy

Hi @Rachana Kandlagunta -- Welcome to the Atlassian Community!

Until we see those...

From what you describe, I suspect your rule looks like this:

trigger: some trigger
action: create issue, for the epic
action: create issue, for a story, setting the parent to {{createdIssue.key}}
action: create issue, for a story, setting the parent to {{createdIssue.key}}
...

When using this structure, {{createdIssue}} is changing as you add each issue. When you instead want to use the same issue as the parent, two solutions approaches are:

After creating the epic, branch to Most Recently Created Issue, and change the sets of the parent field to be the current issue or {{issue.key}} as that will refer to the branched-to issue: the epic
After creating the epic, save it's key in a created variable, and use that when setting the parent field for each issue

Kind regards,
Bill

Rachana Kandlagunta

Thank you Bill.

Rachana Kandlagunta

trigger: some trigger
action: create issue, for the epic
action: create issue, for a story, setting the parent to {{createdIssue}}
action: create issue, for a story, setting the parent to {{createdIssue}}

This is exactly what I have and Only the Epic is created and the 1 story. But I need more stories to be created @Bill Sheboy

Bill Sheboy

Thanks for that information. Please see the two possible solutions I noted earlier, try one of them and re-test.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

automation

jira-service-management