Linked Tasks and Subtasks as Automation Triggers
C
Cam Gottschall
It would be awesome if we could get a number of automations based on the subtasks that are linked to a ticket.
For example, we are looking for a way to update a custom field when the status of a subtask is updated.
I see that there is a trigger for when all subtasks are complete but not one to check for the status of individual subtasks.
Log In
pixojoy
Is this for tasks too, or just subtasks?
I'd like to be able to add a tag for linked ✲tasks✲ through automations. That way, it can show up in my filtered-tags Calendar View for tasks with non-negotiable dates. I feel that this system would help me chip away at my Rocks & Project Goals.
Below is a mockup
Rafael Bolandini
And it would also be very important that we had the possibility of creating specific statuses for the subtasks and that they do not necessarily have the statuses of the mother tasks.
S
Sharon Kirby
Zach I totally agree, from an Agile perspective we are not making our stories as sub-tasks to the Epic, as they require the same statuses. This is a huge limitation.
Zach
Sharon Kirby: I hear you. There's a big feature request here: https://clickup.canny.io/feature-requests/p/different-statuses-for-tasks-and-subtasks for what you're hoping for. We'd need to tackle that first.
Zach
Thanks Cam. We're currently working on allowing you to specify whether or not you want an automation to run on tasks vs subtasks vs both. After that, we can revisit this ask (which others have expressed as well).
C
Cam Gottschall
More generally, we would love to see more enhancements to the automations between a child and a parent ticket.
There is a need for clickup automation options that allow for consequences on a parent based on conditions met by a child
(and vice versa)
C
Cam Gottschall
Additionally, we would love the ability to manage parent child ticket statuses based on the custom field updates as well. For example, if the subtask is updated to
in development
, then we would like to have the ability to update a custom field on the parent with automations.