Feature Requests

Situation: Currently, there is no option to add a formula (custom field) to different locations (lists e.g.). The only way is to dublicate the formula in the new location. Solution: Formula custom fields should be allowed to be added to different locations in the custom field manager.

When creating a new Labels custom field, the current UI requires at least one label to be defined before the field can be saved. This is unnecessary friction because: Labels are designed to be added interactively from within tasks (via "Create new label" in the picker), making them ideal for building a category list organically as you work. Users who are new to Labels may not realize they can add new options later, since the setup screen makes it look like a fixed, pre-defined list (similar to Dropdown). This requirement contradicts the flexible, on-the-fly nature of the Labels field type. Suggestion: Allow users to create an empty Labels custom field with zero initial options, just like how a Text or Number field can be created without default values. Users can then add labels interactively as they assign them to tasks. This small change would make the Labels field more intuitive and better communicate its key advantage over Dropdown: that it's a living, growable list. Thank you!

As part of our system governance, we want to do regular audits of our custom fields. We would like export the descriptions as part of these audits, so that we can review the descriptions for accuracy and identify any fields that are missing descriptions without having to select each one individually. (we have 150+ custom fields and are adding more).

Problem: When using Tasks in Multiple Lists to share tasks across different audiences (e.g., an internal engineering list and an external client-facing list), all Custom Fields from the task's Home List are visible when opening the task detail, regardless of which list the viewer is accessing it from. There is no way to hide specific fields per view or per list context. This creates an information leak: internal fields like "Complexity," "Internal Cost," or "Engineering Notes" are fully visible to external stakeholders (clients, partners) who access the task from a client-facing list. The only workaround today is to not use multi-listing at all and duplicate tasks manually, which defeats the purpose of the feature. Use case: We are a managed services company that uses ClickUp to run projects. Our internal engineering team works from one Space with detailed operational fields. We share project progress with clients through separate lists in a client-facing Space. Multi-listing is the natural solution, but because we cannot control field visibility per context, we are forced to either expose internal data to clients or abandon multi-listing entirely. Proposed solution: Allow Workspace admins or view creators to configure which Custom Fields are visible in the task detail panel on a per-view or per-list basis. When a user opens a task from a specific list/view, only the fields enabled for that context should appear in the detail panel, not just in the column headers. Impact: Without this, Tasks in Multiple Lists loses its value for any organization that needs audience separation (internal vs. external, team A vs. team B). This is a common need for agencies, consultancies, and IT service providers who share project visibility with clients inside ClickUp.

We hit the 500-option limit wall for the Label/Dropdown custom field. For a company who gets hundreds of clients over time, this won't do. We want to organize/categorize our data based on either Label/Dropdown custom fields like "Clients/Companies" as these prevent naming inconsistencies when the Text custom field is used, and provide search capability for existing names that we have catered to.

Hi ClickUp team! I’d like to suggest an improvement to Relationship Custom Fields, especially for workflows that rely heavily on CRM data. When creating a new task, we often need to select related items through Relationship fields, for example: Client / Contractor Venue Label Artist Company The problem is that sometimes the related item doesn’t exist yet. Currently, we have to: Stop creating the current task. Navigate to the CRM List where that entity belongs. Create the new item. Return to the original List. Start or continue the task creation process. Find and select the newly created item in the Relationship field. It would be extremely useful to have a “+ Create new” option directly inside the Relationship field dropdown. For example: Venue Search venues... → Venue A → Venue B + Create new Venue Clicking it could open a small modal or quick-create form, allowing us to create the missing task in the Relationship field’s target List and automatically select it as the relationship, without leaving the task we are currently creating. Why this would be valuable We use ClickUp as a CRM and operational system, with separate databases for venues, clients, labels, artists, bookings, etc. Relationships between these databases are essential. During booking creation, users frequently discover that a client, venue, or other entity hasn't been registered yet. Being able to create that entity inline from the Relationship field would eliminate unnecessary navigation, reduce friction, prevent duplicate records, and make ClickUp much more powerful for relational CRM/database workflows. Ideally, this functionality would also work anywhere Relationship fields are editable, not only during task creation. Relationship field → Search existing item OR create a new one. I believe this relatively small UX improvement could have a significant impact for teams using ClickUp as a CRM or relational database.

"baseline" become a "custom field" in the next release

I have a custom date field for my form that is the date they submitted the form, I want to default it whatever the current date is. Currently when I hit today it sticks to the date that is today and doesn't change each new day.

Custom Fields for Task Types are great but one of the main reasons I would use them is to filter out formulas on tasks in a single list. Because Formula fields are not able to be a Custom Task Type Field it defeats 80% of the use cases I have for Task Type Custom Fields.

I have created many custom fields. It would be great if we can rearrange the custom fields so it will display as we wanted to in the task As you can see in bullet 1, 2, and 3, I have arranged the fields in order Approval Complete Status. But right now, all those fields don't display as order as I wanted, you can see Bullet A, B, and C so you know what I mean