Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Advanced Branching: For Each Smart Value Create a new Story and the subtasks

I'm using an advanced branch to create a new Story for each label added to an Epic but am unable to then also create the Sub-tasks to go with each Story. 

It seems I'm unable to add a Branch rule / related issues component inside of the Smart Value Branch.  If I could move the last branch under the "Then: Create a new Story" this automation would work perfectly.


Screen Shot 2021-07-19 at 5.43.19 PM.png

I get this error in my audit log

Can't branch rule as it requires issues to have been previously created by this rule. More than likely you have not yet created an issue or the issue(s) were created in an another 'If' block or branch - these would then not be visible outside of that block/branch.

4 answers

1 accepted

1 vote
Answer accepted
Joy Chiu Atlassian Team Jul 19, 2021

Hi @Brian Eschen 

This is a known issue: AUT-247 . In "For All created issues" branch, it cannot get the issues created in "For each" branch.


Joy [Automation for Jira]

@Brian Eschen If you click and drag a branch before you specify whether it's an "Advanced branching" or "Branch rule / related issues" component (i.e., while it is just a purple block that says "New branch"), you're able to nest it inside other branches. Jira nested branches.png

Hi @Curtis da Costa 

How much have you tested that structure?

I am asking because...

  • that branch on "current issue" isn't really a branch; it gets executed inline,
  • I have seen other posts from Atlassian folks that nested branches are not supported, and
  • as branches execute in parallel and asynchronously, I wonder if the results of that structure would be unpredictable. 

Kind regards,

@Bill Sheboy I was thinking it would likely be unpredictable as well as everyone seems to be saying it's unsupported.  I've played around with a single nested branch and it solved an issue I was having that was (somewhat, but not really) similar to OPs (I had a "For Sub-tasks" branch nested in a "For Destination issue" branch).  I haven't tested his exact application, but thought it may be useful for him to try it out.

Like Bill Sheboy likes this
0 votes
Daniel Ebers Community Leader Jul 21, 2021

Hi @Brian Eschen

wanting to see the results I gave it a try - it worked for a company-managed project, however I feel sceptical about the implementation because there is no usage of any advanced features. It is so simple that there might be something missing, in case you would like to check and compare it would be appreciated.


For an Epic labeled with "Test" upon manual run of the rule a new Story will be created.
In this Story a Sub-Task will be created. Then the "Test"-label is removed from the issue (to prevent endless-loops) - in accordance to what @Bill Sheboy suggested.
In the next step my intention was to try the JQL-approach Bill suggested but before doing so it turned out the rule seems to work like shown above - anyway, please check :)


0 votes

Hi @Brian Eschen 

I haven't had a lot of success with the related issues branches.  My work-around is to use JQL branches to re-create what the related issues would have returned.  Perhaps give that a try.

Best regards,

Hi @Bill Sheboy Do you have some examples handy? I haven't tried anything like that before.

Thank you!

Not really, as each case is often different. 

Let's assume you uniquely identify your newly created stories (based upon the epic labels) with a value in their own labels, such as "Needs_Subtasks".  Your next piece of the rule would be:

  • branch: on JQL of project=myProject AND labels = Needs_Subtasks AND... any other criteria you needed, such as comparing to the trigger issue (epic) as parent/epic link
    • action: add sub-tasks
    • action: edit issue to clear the Needs_Subtasks from the labels

That last edit is the stopping condition, so the same issues do not repeatedly get more sub-tasks added later.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events