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.

From Support Ticket: User wants to use a Form to create subtasks on a task, rather than a new task in the List

We have moved from subtask heirarchy for most task types to using relationships, so we are not held to subtask limits and have a better categorization of those links/associations. There is two big problems we've been running into with the Related section: 1) Can't select tasks - this is a massive one as we can simply select a task to change a field or conduct any action, and even more of a problem when you need to bulk update multiple tasks. Selection checkbox is a key feature and should be here especially when i've had ClickUp tell me best practice for use cases was to use relationships. 2) Add Columns needs more options - relationships for example, don't seem to be enabled anymore, and they were before but didn't work (I recall enabling a relationship field column and not seeing any results populating when clicking in to it). Regardless, having all columns available to add, as well as ensuring that relationship fields can populate correctly the list of options is a big help (especially when paired with bulk editing). When you start using relationships, you find yourself constantly linking tasks, so having those relationships accessible is key. 3) Sorting - currently you cannot sort or group tasks within the related tab. Again, if relationships are a key part of the platform flow, then there should be at the very least a way to sort the list. 4) Navigation Issue - we get constant issues within our team of users clicking on a task within the Related tab, then not knowing how to go back and clicking "x" thinking that the previous task that was associated to it was still open. For example. If im on a User story task, i may have build tasks associated with it through a relationship, and on the related tab I want to update a few of them. I click on the first, make an update, click x, and now have to hunt down the previous one (especially if its not saved to the tray). I have gotten in the habit of opening tasks up in new tabs, however then you have a ton of tab switching. Not sure if a better approach would be to not close out the task to begin with. If im on a user story, and i click on a related task, have the new one open up on top, once i close that, the previous task is still open, and i can close that once im done. I think that could enhance the user experience greatly and mitigate a lot of confusion on finding where you were and constantly going back and forth - just leave the task open until x is clicked.

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

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.

We cannot currently pull relationship or rollup fields into Dashboard reporting. We are using relationships & rollup fields to keep regularly updated fields up to date across all lists/tasks (i.e. if a person's manager changes and they're also on our training waiting list, we only have to change the manager in one place but the info flows through to the linked task in the waiting list as well). For example, I'd like to be able group a dashboard chart by manager to see how many people with the same manager are on the waitlist (or from the same team, in the same level, etc.).

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!

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.

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)