Automation at the TASK LEVEL
under review
M
Mukul Singh
Right now, automations are done at the list level. This gives far less control since every task in that last would be subject to that automation. I am suggesting that automations be done at the TASK level so that you can set something for just 1 task.
Log In
Евгеній Совяк
In fact, this would already become a full-fledged ERP system, and would greatly simplify our life in building business processes. Absolutely all processes of any business can be given logic and sequence of execution, which will eliminate the human factor. Cool, we are waiting.
S
Stephanie Henry
Yessss! It's frustrating when you have ONE task that needs a little extra something, but you can't because it would apply to the entire list, ugh 😒 Or worse, the thought of creating a whole extra list for just one task... double yuck.
Zach - ClickUp
under review
Jonas Veltman
Any Updates on this one? Would make my team MUCH more efficient, if we get this! Caroline Ginty can you share anything?
Jess Blinn
This feature is CRITICAL to streamlining our workflows. We're coming to ClickUp from Canopy, which has a very sophisticated system of automations for tasks - and subtasks!
As an example: we use task templates frequently. When a certain task is created from a template (let's say, the task is for a sales call), I want the sales team to be assigned to that task automatically, and to their individual subtasks as well. I don't want to assign them in the template because then they will see a bunch of templates in their work lists.
Another example of an automation that we'd use every single day is the ability to determine at the task level that if all subtasks are completed for a specific task, the parent task is automatically marked complete.
There are many, many use cases for this. Automations at the list level are far less useful.
PLEASE add this!
Caroline Ginty
Hi everyone! I wanted to let you know that we are currently working on a similar feature request (https://clickup.canny.io/feature-requests/p/custom-buttons-for-triggering-automations), which will allow you to create a new Custom Field type, Button, that when clicked, will trigger an Automation for a particular task. I know this feature request for Automation at the task level encompasses other asks as well, but I wanted to make you aware so anyone interested can follow along on the other thread for updates. Cheers!
S
Stephanie Henry
Caroline Ginty that link says "There is no such post." 😁
Jonas Veltman
Caroline Ginty is this still WIP? I cant find the post either, you're referencing to
Caroline Ginty
Stephanie Henry Jonas Veltman Can you try now? I'm able to open it on my side!
Jonas Veltman
Caroline Ginty no, still “no Post” ist this feature still in development though?
Maggie Houtz
This would greatly improve one of my workflows in particular. I use ClickUp to manage programming for a bimonthly online radio show and use a List template that includes all the steps of programming - starting with booking the artist. If I was able to set an automation on the "Book artist" task so that when its status is changed to "Confirmed", I would trigger the action of setting the due date for the next task in the list. Right now I cannot specify at this level which means I must manually enter these dates for each show.
Ghaniya Shaikh
Right now, automations are done at the list level. This gives far less control since every task in that last would be subject to that automation. I am suggesting that automations be done at the TASK level so that you can set something for just 1 task.
Devon Moran
Merged in a post:
Allow automation on a single task (to be used in a template)
Julie Runez
We have project templates that include a task for shipping. We would like to be able to create an automation that will notify our customer service team to set a date for a customer satisfaction follow-up once that one task is marked complete. It appears now that the automation would have to be applied to EVERY task in the task list, which would be overwhelming and inefficient.
K
Kevin McCuen
Allow me to add another use case and example for this feature.
We are currently using a list to manage our IT renewals. I want to be able to automate that when the status changes to 'x' (list level automation) a task level automation sees the status change and can assign 'y' users and 'z' watcher(s) without the use of a 3rd party tool. Each task in this list is a specific and separate renewal item like Adobe, MS365, ClickUp and all may have a different owner.
To address the management of each automation I would suggest an automation manager (like the custom field manager) that the first indicator is WS (Workspace), S (Space), L (List), T (Task) with the ability to sort like we do in a folder or list. This would also mean that users would need to name their automation, so it's probably a can of worms.
Load More
→