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 

[Bill Sheboy · Accepted solution]

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:

1. 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
2. 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.

[Rachana Kandlagunta]

Thank you I want to go with this 

1. After creating the epic, save it's key in a created variable, and use that when setting the parent field for each issue 

What do I mention for 

1. Variable Name

2. Smart Value 

Thank you @Bill Sheboy 

[Bill Sheboy]

For variable name, use something to clarify the meaning.  For example:

• variable name: varEpicKey
• smart value: {{createdIssue.key}}

Then in the story creates, use this for the parent value:

{{varEpicKey}}

[Rachana Kandlagunta]

This is excellent and worked like MAGIC! Thank you a ton @Bill Sheboy :)

[Rachana Kandlagunta]

na

[Bill Sheboy]

Hi @Rachana Kandlagunta 

I recommend creating a new question for things like this, rather than adding on to already resolved ones.  That will help more community members to see it and to offer suggestions.

For your first use case, you could use a single rule, with branching and conditions to solve this.  For example...

• trigger: field value changed
• branch: to current issue
  • condition: check if a specific value is checked
  • action: create the epic
  • action: create the story
• repeat above, for each checked value...

For your second use case, there is a clone action for rules, and the specifics of your scenario will determine if it can be done, and how many rules will be required.

[Rachana Kandlagunta]

Thank you so much. Will try and let you know @Bill Sheboy 

[Rachana Kandlagunta]

na

[Bill Sheboy]

@Rachana Kandlagunta -- Please stay with the thread in the new question, as Mark was describing what is / is not possible when using forms.  Thanks!

[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!