Feature Requests

Add the ability to apply folder and space templates via the "Create Folder" and "Create Space" automation actions, similar to how you can now apply list templates in the "Create List" action (with date remapping, import settings, etc). This would let you spin up entire folder or space structures automatically when triggered by status changes, forms, scheduled dates, and more.

We would like the ability to make custom fields dependent on each other in the same way that tasks are now.

I would like to request the ability to assign different holiday calendars to different users, teams, or regions within a single workspace. Currently, only one holiday calendar can be applied workspace-wide, which does not accommodate organizations with teams in multiple countries or regions. Why this is important: Our teams operate in different countries, each with its own set of public holidays. We need workload and utilization reports to accurately reflect each person’s true availability, based on their local holidays. Applying a single holiday calendar to all users leads to inaccurate reporting and scheduling. Suggested Solution: Allow admins to assign a holiday calendar per user, team, or location. Ensure workload and utilization calculations use each person’s assigned holiday calendar to determine available hours. This feature would greatly improve resource planning and reporting accuracy for global teams. Thank you for considering this request!

The recent accessibility change has killed the ability for us to use yellow as a status color. It is forced into this muddy color instead. The visibility was actually better BEFORE the change. If a custom color is selected for status, that should override any so called "accessibility" enhancements.

Currently, when we create a task type, it becomes available across the entire workspace. This creates issues for standardization, as we want to enforce the use of specific task types within certain lists and even based on location. We’d like the ability to restrict task types to a list or location, so team members only see the relevant options. For example, in some cases, we only want three task types available within a given list. This functionality will help us: *Enforce consistency in how tasks are categorized. *Limit confusion by only presenting relevant task types. *Better leverage the beta functionality of fields tied to task types. IMPACT: Without this, team members can select incorrect task types, leading to data inconsistency and reduced effectiveness of field-based reporting and automation. REQUEST: *Ability to configure which task types are available per list, space, and/or entire workspace. Include the ability to manage ClickUp-created task types, such as Task, Milestone, Meeting Note, Key Result, Person, etc.) --By Location (Department/Team/Region): For example, the Sales – Europe list may only need three task types (“Lead,” “Demo Scheduled,” and “Contract Sent”), while Sales – US might require a different set. Restricting by location would keep task types relevant for each group. --Space: If an organization manages multiple workspaces (e.g., Operations vs. IT), admins could enforce different task type sets per workspace. This would prevent irrelevant task types from appearing in the wrong context (e.g., IT-specific types showing up in Sales). --Workspace: We may want to make certain task lists available across the workspace still. *Add to the space configuration/creation to set the task types available for each, in case there are no task types available at the workspace level.

Main task progress should be cumulative total of subtask rollup (similar to time rollup)

Many teams — agencies, system integrators, consultancies — work on behalf of external clients. Today, there is no native concept of "client" in ClickUp. Giving a client visibility into their own tasks requires manually creating dedicated lists or spaces, configuring permissions per project, and maintaining that setup over time. Grouping or filtering work by client across the workspace is simply not possible natively. The proposal Introduce a new user type alongside the existing Guest: the Guest Client. The workflow would be simple: Invite an external user by company email and define them as Guest Client Associate that Guest Client to any task using a native field — similar to Assignee — selectable, filterable, and groupable across all views and dashboards When the Guest Client logs in, they automatically see only the tasks where they are associated — no manual filtering, no dedicated spaces, no permission configuration required Why this matters This is not a CRM request. It is a minimal extension of what already exists — the Guest user type — with a semantic distinction and a native field behavior. The infrastructure is already there; what is missing is a role that maps to a real-world actor (the external client) and that ClickUp can use as a first-class axis for filtering, grouping, and access scoping. Without this, teams working for multiple clients are forced into workarounds: dropdown fields with hard 500-option limits, duplicated list structures, or manual permission management that breaks at scale. None of these solutions allow answering the simple question: "Show me everything we are doing for Client X." Expected outcome A Guest Client user type that: (1) can be assigned to tasks as a native field, filterable and groupable exactly like Assignee across views, dashboards, and reports; and (2) whose login experience is automatically scoped to their relevant work — turning ClickUp into a native client collaboration layer without adding complexity for the internal team.

I would like to be able to have my Super Agent create a folder and an associated list. Today it can only create a lists.

A Gallery view would make a useful addition to the Time, List, and Board views. In the Gallery view, tasks would appear on cards, just like the existing Board view, but without constraining cards to columns. Board view is good for workflows. Gallery view would be good for filtering and browsing. The important thing to realize is that tasks don't always get done in order, and some don't require a workflow. A reading list is one example of a use case in which I might want to filter and browse tasks in a gallery view. Choosing the next blog topic for an editorial calendar is another. The screenshot shows an example of the gallery view used in Airtable. This example happens to show recipes—another example of 'tasks' I might want to filter and browse.

I've added this a couple of times, but as the team continues to use Clickup, there is a lot of items missing in tracking and forecasting. I've tried all the widgets but ideally this is what I need: for any given month (and possibly other time frames): a list of projects containing how much time was logged on that project by assignee or resource a list of resources containing how much time they logged on each project they worked on