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 created an automation on when an issue is created. When I am inside an Epic, I clicked the + to create a sub-issue 'Task'. I know it has a parent because I created it from the Epic. However, I get an error.
Hi Laurie, that is what I want to accomplish! However, when I run the automation i get the output "No Action Performed". It's almost like its a timing issue. It runs the automation before the sub-task has a parent and it says there is no parent. and then it will link it to a parent after the automation
Hi @Spencer Hoyle -- Welcome to the Atlassian Community!
Adding to Laurie's answer...
The issue created trigger can fire so quickly that the data is not available for the rest of rule processing...such as using the parent issue's data.
The work-around / fix for that is to always add the Re-fetch Issue action after the Issue Created trigger. This will slow down the rule by about one second by reloading the data before proceeding.
@Laurie Sciutti -- Spencer noted this was the child issue of an epic, and so the condition you show for a sub-task seems incorrect. What about this instead: