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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi @심 여울
Welcome to the community!
Hard to tell what it is you are trying to achieve with this rule, but here are a couple of thoughts.
you should have the condition before the action. Trigger>condition(s)>action otherwise the condition will achieve nothing, as the action will have already have been applied and the condition has nothing to them action upon.
By the looks of it you are wanting a rule that: when the "action" and "item" label is added to an issue (any issue) it will be cloned to the "23 action items Tracking" project. Is that correct?
@심 여울 ,
Could you please share what exactly you want to do with this automation rule? Because the way that you done, it seems like the condition should be before the action.
Please, tell us more about the ideia behind this automation rule and we can help you to fix this.
Regards,
Fernando
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.