Feature Requests

As a workspace administrator, I regularly need to rename, replace, or remove custom fields as our processes evolve. The problem is there's currently no way to determine where a custom field is being referenced across the workspace. Dashboards, views, automations, and forms can all be configured to use a specific custom field, but there's no reverse-lookup to tell me which of those are affected before I make a change. Right now, the only option is to manually open every dashboard, every view, and every automation to check whether a given field is in use. In a large workspace with dozens of dashboards and hundreds of views, that's not realistic. It means admins are either spending hours auditing by hand or making changes and hoping nothing breaks. What I'd like to see is an impact analysis tool, ideally accessible from the Custom Field Manager, that shows everywhere a custom field is referenced. Something like: + Dashboard cards using the field (as a filter, grouping, or data source) + Views filtering or grouping by the field + Automations referencing the field in triggers, conditions, or actions + Forms that include the field as a question + Super Agents that have the field as a reference or are programmed to update the field This would give admins the confidence to clean up, consolidate, and improve their custom field structures without the risk of silently breaking downstream reporting or workflows. It would also make onboarding new admins much easier, since they could understand field dependencies without institutional knowledge. I imagine this would be valuable for any workspace at scale, but especially for teams on Business Plus and Enterprise plans where custom field governance is a real operational concern.

I would like to hide the empty native fields at the top of my card: Assignees, dates, and time tracking

Do not collabse Label custom field if it not necessary. Like on the picture - I can see them all - there is enough space.

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.

Feature Request: Duplicate Labels Custom Field with options and task values When duplicating a Labels custom field, only the field shell (name, type, visibility, locations) is copied. The label options and per-task values are not carried over, resulting in an empty field. For a list with 135+ tasks where each task has 3-4 labels, manually recreating the options and re-assigning values is not feasible. This is a basic database operation (column duplication with data) that should be handled natively. Current behavior: Duplicating a Labels custom field creates a new field with no options and no task values. Expected behavior: Duplicating a Labels custom field should copy all label options (with colors and order) and all per-task values to the new field. Use case: We needed to split one Labels field into two (primary owner vs. supporting teams). The only workaround was to use ClickUp Brain to copy values task-by-task via API, which took over 10 minutes for 135 tasks. A native duplicate-with-values feature would complete this in seconds. This applies equally to Dropdown custom fields.

It would help me greatly to be able to inherit custom fields and its input into other tasks. Just like when I open a new list and it asks " would you like to inherit status" there should be an option of inheriting custom field inputs. As it is I am spending a lot of time inputting data into my custom fields.

It would be great to track total time in custom fields much like the time in status tracker that is already available

Currently, ClickUp automatically formats Number custom fields with thousands separators (commas). While this formatting is useful for many use cases, there are situations where commas are unnecessary or create visual inconsistencies, particularly when the field is being used for identifiers, reference numbers, job numbers, project codes, invoice numbers, or other non-financial values. It would be extremely helpful to provide a formatting option that allows administrators to choose whether a Number custom field displays with or without thousands separators. Example: * Current: 12,345 * Desired Option: 12345 Benefits: * Improves flexibility of Number custom fields across different use cases * Better supports project IDs, job numbers, invoice references, and tracking numbers * Creates consistency with external systems that do not use comma formatting * Reduces confusion when numerical values are intended as identifiers rather than quantities or currency * Improves reporting, exports, and visual presentation of operational data Ideally, this would be a field-level setting that allows Workspace Administrators to select whether thousands separators are displayed, rather than applying a single formatting standard across all Number custom fields. This enhancement would make Number custom fields significantly more versatile for operational, financial, project management, and reporting workflows.

Be able to have a custom field that works on the same logic as the “Time estimate”

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.