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.
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.
Automation rule not kicking in when changing issue to a sub-task
Hi everyone
I'm trying to create an automation rule that will clear out certain fields when an issue is converted to a subtask, and the rule just doesn't seem to get triggered at all. Unsure what I'm missing. Any ideas?
I've tried using a condition to check the "Type" field itself for when it's changing value to "Sub-Task" as well as using smart values. Nada. Is a change to a sub-task not considered a field change maybe?
3 answers
1 accepted
Thanks @Mark Segall . I've tried that instead of a Value Change, but the Move only captures movement of an issue between projects. I've tried it anyway, though, and still nothing in the logs. I tried this with both the issue type check and smart values.
Are you able to get something like this to work? If so, would you be able to post a screenshot of the rules?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.