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.

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.

From Support Ticket: I can't automate status change or anything based on email thread (eg WHEN New Email received THEN change status)

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'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 :).

Modern teams generate ideas, requests, questions, and improvements every day. For businesses dealing with intellectual property lawyers new york https://pearllemonlegal.com/intellectual-property-law-firms-new-york-usa/ keeping information organized can also make collaboration around important work much easier. A well-structured feedback space gives people a clear place to share suggestions without allowing useful ideas to disappear in scattered conversations. The feedback environment is organized around boards, categories, requests, and roadmap stages. This structure makes it easier to see what has been suggested and understand how different requests are progressing. Users can browse areas such as feature requests, integrations, mobile improvements, languages, and other specialized boards. The roadmap also separates ideas according to stages such as planned, building now, and completed. That approach creates a simple connection between an idea and its current status. For teams, this kind of visibility can reduce confusion when several people are working on related improvements. It also gives contributors a way to understand whether a particular request has already been raised. Many feedback systems become difficult to use when suggestions are repeated across different channels. A searchable board helps people discover existing discussions before creating another request. Comments and votes can also provide additional context about why an idea matters to different users. Another useful aspect is the separation of feedback into focused categories. Different areas can be reviewed independently while still remaining part of a larger feedback system. The roadmap format also provides a straightforward way to follow changes over time. Completed requests can remain visible as part of the history, while planned ideas show what may receive attention later. This creates a more transparent flow from suggestion to discussion and eventually to implementation. For organizations, a similar structure can help keep conversations focused and make follow-up easier. Clear titles, concise descriptions, and relevant categories can make individual requests easier to understand. A consistent process also helps teams distinguish new ideas from existing discussions. Ultimately, useful feedback depends on more than collecting comments; it requires organization, context, and visibility. A structured workspace can provide those elements without making the process unnecessarily complicated. The result is a clearer environment where ideas can be shared, discussed, tracked, and reviewed over time.

I would like to see Click up add a way to add an approver to a specific task.

I'm using automations to trigger a webhook to notify my AI agent when things happen in Clickup. However, there are two holes so far: (1) Adding a threaded comment doesn't trigger the automation (2) There's no automation trigger available for @mention. Desired outcome: Add a @mention trigger to automation triggers so a webhook can fire every time an account is mentioned in a comment or elsewhere. Add support for nested comments to the comments automation trigger.

Two things need to happen. Multiple api keys. Let us create multiple. Now we can only create one api key at a time, and when we need the key, we need to rotate the old one, which breaks existing automations, forcing us to replace it everywhere it was used. Per key permissions: read, write is a bare minimum, otherwise more granular, like creating tasks, comments, deleting, etc. Ability to read older keys. Ofc this one's optional, but maybe you can make old keys readable only if they are not "full permission" or if they are with read-only permissions. I'm surprised this is not a bigger request. The MCP does not do the job the same way the API does, we need proper API access and as far as I see now there is no traditional multiple key management. Maybe you can put these things behind a warning if security is the fear