You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
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.
How much have you tested that structure?
I am asking because...
@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.
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 :)
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:
That last edit is the stopping condition, so the same issues do not repeatedly get more sub-tasks added later.