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
Hi @Rahul ,
This is exactly how I'm using automation. You can do that and much more!
You can create them as children of the issue that triggered the automation or they can be completely unrelated.
At a really high level I would do this:
Trigger: Issue Transitioned
Condition: Issue does not have any subtasks
Action: Create 3 Subtasks, using the summary and due date from the issue that triggered the automation
There are other considerations such as, should it apply to issues on one project, multiple projects or globally? Should it run if another automation rule triggers it?
Couldn't agree more with this response. Only addition I would make is to check for the Sub-task Summary so you're not duplicating sub-tasks every time you transition the issue.
Thank you @Mathew Lederman ! This is what I was attempting to do by checking that subtasks are not present on the issue that triggered the automation , but comparing the summary would be a more robust solution for this.