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.
Join now to unlock these features and more
Hi @Jenni Chen
It is possible this is a timing issue. The Issue Created trigger can fire so quickly the issue data is not available at the time the rule runs. This can cause later rule steps to not work as expected; for example, perhaps the parent is not visible / set yet for the copy of Components.
The work-around for this is to always add the Re-fetch Issue action immediately after the Issue Created trigger. This will slow down the rule by about a second and reload the issue data before proceeding.
Please try that to see how it impacts the results.
Please move the Re-fetch up to immediately after the trigger, and then re-test:
Please show images of your Edit Issue action and the audit log details showing the rule execution. Those may help to explain this.
Also, is this a company-managed or a team-managed project? You may find that information at the bottom-left side of the page's expanding area.
After you create the issue the component should be changed to the one from parent - but the rule is only run at the moment you click create at the bottom of issue create form.