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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Join us to learn how your team can stay fully engaged in meetings without worrying about writing everything down. Dive into Loom's newest feature, Loom AI for meetings, which automatically takes notes and tracks action items.
Register today!Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.