Feature Requests

Hello, if I keep ClickUp idle for a while there is a new popup saying "It's time to update ClickUp!", which I've never seen before, appearing on the bottom-left corner of the interface and interfering with the possibility to open items in the navigation menu, especially when using the "search" functionality (which I need because I have hundreds of lists to browse in my spaces - in the attached picture the item hidden by the popup is exactly what I need to get to). it seems it just wants me to refresh the page since I've tried checking for software updates and my application is already up-to-date. I find it annoying and useless and wish to be free to choose when to have the page changed or refreshed as it happened until yesterday, but I can't find a way to permanently get rid of that message.

The similar terms "Space" and "Workspace" are confusing to a new user! I suggest renaming "Workspace" to "Realm."

I enable the ID for a space where my design and tech work together. But the ID is not necessarly for the design, can I disabled it from the list design ?

Hello ClickUp Team, I’d like to request the ability to set custom hex colors for Folder icons, similar to how we can for tags and other elements. The current default color palette is quite limited, and being able to use specific brand or project colors (for example, #00d0ff) would help with organization and visual consistency across our workspace. Is this feature on your roadmap, or are there any plans to expand color customization for Folders? Thank you for considering this request! Best, Cameron Denny

It would be helpful if the sidebar and the main section had a stronger contrast. It's hard to focus when sections are so close in color. Also, allow us to adjust the contrast. The theme settings are too limited. WordPress does a good job with this, and ManageWP just updated its dashboard to use a contrast effect. https://managewp.com/ui-update-ea-release/

Automation to convert tasks into subtasks based on folder or criteria Currently, it is not possible to create an automation that: Detects a task created in a specific folder, and Automatically converts that task into a subtask of an existing parent task, based on criteria such as task type, folder, or custom field values. This limitation is especially problematic in workflows where tasks are generated externally (for example, incoming legal notices) and must be consolidated under a single main project or case. Suggestion: Introduce an automation action that allows a task to be converted into a subtask of a defined or identifiable parent task, using conditions such as: Folder or list Task type Custom field values This would enable fully automated hierarchical organization for complex, event-driven projects. ---- Em português Automação para converter tarefas em subtarefas com base em pasta ou critérios Atualmente, não é possível criar uma automação que: Detecte uma tarefa criada em uma pasta específica; e Converta automaticamente essa tarefa em subtarefa de uma tarefa pai existente, com base em critérios como tipo de tarefa, pasta ou valores de campos personalizados. Essa limitação é especialmente problemática em fluxos nos quais tarefas são geradas externamente (por exemplo, intimações recebidas) e precisam ser consolidadas sob um único processo ou projeto principal. Sugestão: Criar uma ação de automação que permita converter uma tarefa em subtarefa de uma tarefa pai definida ou identificável, utilizando condições como: Pasta ou lista Tipo de tarefa Campos personalizados Isso possibilitaria uma organização hierárquica totalmente automatizada para projetos complexos e orientados a eventos.

It should be possible to set an alphabetical sorting for folders within a space which would run everytime a folder is added/created. Right now you have to do this manually each time! This is almost ridiculous!

In multi-workspace setups, teams often separate high-level portfolio management (e.g., Projects and Releases) from detailed product backlogs (e.g., Epics, Features, and User Stories). Currently, when nesting tasks from one workspace as subtasks under a parent task in another workspace, the child tasks automatically inherit the parent's workflow (statuses). This forces teams to use the same workflow across workspaces or avoid proper nesting altogether. We request the ability for nested tasks (subtasks) to retain their original workflow independently, even when the parent task belongs to a different workspace with a completely different workflow. Proposed behavior: Subtasks keep the workflow (statuses, status categories, automations tied to statuses) of their original task type and workspace. No inheritance of the parent’s workflow unless explicitly enabled via a toggle (e.g., "Inherit parent workflow" option). Other elements like custom fields can continue behaving as they do today (we are primarily requesting workflow independence). Why this matters: Current alternatives like task relationships (linked tasks) are not sufficient because: They are not visually prominent in the UI (no clear hierarchy in List/Folder views). Time tracked on related tasks does not roll up or display together, making it impossible to accurately calculate real effort and cost at the project/release level. Dependencies and blockers are harder to manage and visualize without a true parent-child structure. Key Benefits: True hierarchical visibility: See an entire project with its Releases, Epics, Features, and Stories nested underneath in one view. Accurate effort and cost tracking: Time entries from all nested levels roll up properly for realistic project costing. Faster blocker resolution and progress monitoring across teams. Maintain specialized workflows per team/workspace without compromising structure. Reduced need for workarounds (duplicated tasks, manual linking, external reports). Real-World Use Case: Project Portfolio workspace: Contains "Project" and "Release" tasks with a simple workflow (Planned → In Progress → Testing → Done). Product Backlog workspace: Contains Epics, Features, and User Stories with an agile workflow (To Do → Refinement → Ready → In Progress → Review → Testing → Done). Teams want to nest Epics and Features as subtasks under Projects/Releases for clear portfolio oversight and cost tracking, while keeping the development team’s detailed agile workflow intact. This enhancement would significantly improve ClickUp’s capability to support scaled agile and portfolio management in complex, multi-team organizations. Thank you for considering this — it would be a game-changer for many enterprise and growing teams!

Comments from sub-tasks need to be synced to the main task for continuity

It would be incredibly helpful to have the ability to create folders within folders, as well as store Docs directly inside folders. As our workspace continues to grow, organizing content at a deeper level becomes increasingly important. Nested folders and folder-level Docs would allow teams to better structure projects, reduce clutter, and make information easier to find, especially when managing multiple clients, initiatives, or long-term workflows. This added flexibility would significantly improve overall organization and scalability within ClickUp.