Create Subtask through Automation
Muhammad Jamil
When a task has a certain status, it should be moved to another place as a sub-task of other task.
Log In
J
Jack Sanchez
Once the task has the appropriate status, use the features provided by your task management system to move sonic exe to the desired location as a sub-task. This might involve dragging and dropping the task under the target task or using specific options like "Indent" or "Promote to Sub-task" provided by the tool.
Zach
Muhammad Jamil So you'd like it to be MOVED under an existing task? Or are you saying a brand new subtask should be CREATED under an existing task? I'm a tad confused on this one so I would appreciate understanding your use case here!
K
Kevin Hennessy
Zach:Yes, and moved to then become a subtask of another task.
Muhammad Jamil
Kevin Hennessy: For example, I have a task in a list named Development Sprints, when the task reaches to the status named "Ready for deployment", it should automatically move to another list named "Deployment Pipeline" and become a subtask of a task under To Do status of this list (I can manually specify which task will become parent task).
In short, what Kevin Hennessy said above is correct.
M. Grossberg
Zach: I would like that when a task moves status a new Subtask should be Created in that task
Sandra Diaz
Zach: I can think of a use case for "moved" at our organization. But I can see how having the ability to set up a rule/automation for "created" would be useful too.
Zach
Since we already have "Create subtask" it seems like a "Move to task" with the functionality of moving it under an existing task would do the trick?
M
Miriam Daub
Zach: following up here - 'Create subtask' requires you to select the specific parent task under which the subtask will be created. It can't be dynamic to add a subtask under any given task that is triggering the automation going forward.
M
Miriam Magid
M. Grossberg yes!!
M
Miriam Magid
Zach creating a subtask via automation but not allowing it to be a subtask under the new task seems so obvious! for example, I often have automationsthat create a new task, let's say based on a form or template. i need the next step in the workflow to be created as a subtask under that new task. instead, it wants me to select an existing task as the parent task, which defeats the whole purpose for a workflow where next steps get automatically created
M. Grossberg
Miriam Magid Exactly my point!
Noah James
Zach YES! This would be a phenomenal add. Mostly because when I'm building out Roadmaps for larger projects which include Attachments, using the Create a Subtask automation removes the Attachment, or will only add back a Link to the previously attached File to the newly created Subtask. This then requires me to have to go back and manually download and re-attach all the Files I already attached previously from the links it generates which isn't scalable. For example, when working on Game development, I might pull several assets from my Portfolio List. All those art Files then have to get added back manually and sort of ruins my process.
I use a Parent Task as the "Roadmap" on a List called Roadmaps -- and any applicable Tasks that I want under a specific Roadmap that may be sourced from multiple Lists, to fall under it as Subtasks once moved to the Roadmaps List. I currently have to do this manually. I don't want to create a new List for each Roadmap and I like having them all in one location. So the ability to take a Task and "Convert to Subtask" or "Move to Task" with an automation (depending on a conditional Custom field for example which will dictate which Task it gets Moved to and becomes a Subtask), with all the other fields remaining the same, would be
chef's kiss
TL:DR the ability to fire an automation that will convert an existing Task to a Subtask or "move it" to a designated "parent task" with all fields in tact, would be the bees knees.
R
Ralph Stokes
You can already create sub-tasks but it seems to me you want to move the task which has had the status changed (or add it) to another list and convert it to a sub-task and specify the parent.
I think the real problem is that a task cannot be a task on one list, and a subtask on another list - I have this probelm all the time, it's very annoying.
However, in this case it seems like a "convert to sub-task" action is needed. Then you could automate the following actions: Convert to sub-task -> Move to list. You'd also need the ability to choose the parent task in the "move to list" action.
I think if sub-tasks and tasks were completely interchangeable that this would really improve click up a lot.
Andre Liem
There used to be automations to create subtasks. I still have one that is active, but when I tried to create another automation that creates a subtask it's not available anymore as an option.
C
Christopher Broderick
Andre Liem: Works for me on Business Plus. It may be your subscription level?
Zach
Andre Liem: Create subtask should be there for you.
Andre Liem
Zach: Thanks. I can see it now, for some reason before it wasn't showing up for this project.