Feature Requests

--------------------------------- 🔍 Overview --------------------------------- ClickUp's current status system follows a linear progression model with tasks moving sequentially from one status to the next, right? Well, real-world business processes often require dynamic, multi-path workflows with conditional transitions. To bridge this gap, I propose an advanced visual workflow builder—similar to Jira’s workflow editor—that would provide greater flexibility in managing statuses and processes. --------------------------------- 🎯 Key Benefits --------------------------------- 🔹 Non-Linear Transitions – Move beyond the A-to-B status system and allow multiple pathways. 🔹 Visual Workflow Mapping – Enable teams to design and visualize workflows using a drag-and-drop builder (possibly leveraging ClickUp Whiteboards). 🔹 Conditional Status Progression – Set requirements (e.g., field completion or approvals) before tasks can transition to the next stage. 🔹 Native Automation Integration – Leverage ClickUp Automations to streamline process execution. (Technically, it would be possible out of the box but there's room for extension.) 🔹 Improved Process Control – Spaces could define custom process rules, ensuring compliance and structure in task management. --------------------------------- 📌 Suggested Features --------------------------------- 🔹 Visual Builder – A flowchart-style interface for designing workflows intuitively. 🔹 Flexible Status Paths – Allow statuses to branch into different paths based on rules. 🔹 Automated Transitions – Integrate workflow steps with ClickUp Automations for hands-free status updates. 🔹 Conditional Logic – Require specific conditions (fields, approvals, dependencies) before tasks progress. 🔹 Field Locking – Lock down fields after a particular status of the workflow. 🔹 Whiteboard Integration – Embed workflows into ClickUp Whiteboards for real-time collaboration. --------------------------------- 📈 Long-Term Vision --------------------------------- This feature would elevate ClickUp’s workflow capabilities, making it a more powerful tool for more complex business processes. Over time, it could evolve into a fully conditioned process engine, allowing teams to enforce rules and possibly integrate with the upcoming Teams Hub vision, automate tasks, and finally create more bespoke operational flows. --------------------------------- 💡 Why This Matters for ClickUp Users --------------------------------- 🔹 Enhances Workflow Flexibility – Supports non-linear, adaptable processes. 🔹 Boosts Productivity – Reduces manual status management, enhances automation and authenticity to a status being changed. 🔹 Improves Collaboration – Helps teams map out and enforce structured workflows. 🔹 Aligns with Business Needs – Brings ClickUp closer to enterprise-level workflow management tools.

Please create an option to automate removing a task from additional list

Need ability to restrict who can and cannot see and who can and cannot change Automations. Automations should still be able to run when conditions are satisfied, but their existence should be made invisible to selected users or roles if/when necessary.

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.

Hi ClickUp Team, I am building complex operational workflows and managing different production teams within ClickUp, but I am running into two major structural limitations that significantly increase manual work and clutter. I would love to suggest the following features: Advanced Conditional Logic (If/Else) & Bulk Duplication for Automations Currently, to trigger different actions based on a single condition (e.g., assigning User A if Task Type is "Image", or User B if Task Type is "Floor Plan"), I am forced to duplicate the exact same automation multiple times. This creates an unmanageable volume of redundant automations. The Solution: Introducing "If/Else" branching paths within a single automation would solve this completely. Alternative: If conditional branching is too complex to implement soon, please add a feature to bulk-duplicate or mass-deploy automations across multiple Lists and Folders. Manually recreating them to cover all conditions is highly inefficient. Link Custom Statuses to Specific Task Types Right now, statuses are bound to the Space, Folder, or List level. However, different Task Types living in the same List often require entirely different workflows. The Solution: Allow us to map specific Status workflows to specific Task Types. For example, Task Type X should only display its relevant "X Statuses", while Task Type Y in the same List only shows "Y Statuses". This would prevent users from seeing a massive, confusing dropdown of irrelevant statuses, keeping the UI clean and operations error-free. These implementations would drastically reduce administrative overhead and make ClickUp much more scalable for enterprise-level operations. Thank you for considering!

I have many automations with descriptions, and scrolling through them to find the one I need is a pain. It would be helpful to have a 'Search automations...' function, similar to the 'Search tasks...' feature in views.

I'd love to be able to apply automations on a global level (across the whole workspace). The way our company uses ClickUp means that we want each space to have the same "features", are organized the same, and are utilized the same. This means whenever I create a custom automation for one space, I then have to manually add it to all of our other spaces. We have quite a few spaces, so it takes a while. Having the ability to apply automations to a whole workspace would save a lot of time :).

"Comment is added" only fires for top-level comments. When someone replies inside an existing comment thread, no automation runs at all. Request: Fire "Comment is added" for threaded replies too, or add a "Reply is added" trigger, with a choice between top-level comments, replies, or both. The API webhook taskCommentPosted already fires for replies, so the event exists. It just never reaches Automations.

When a subtask is created, I wish there was an option for it to inherit the custom field from the parent task, today I can't create that! , today you have the option for the parent task to follow the dates of the subtask, if there is something like that for them to follow the fields of the parent task it would be great!