Feature Requests

FEATURE REQUEST Allow tasks connected through a Relationship to automatically sync selected Custom Fields. CURRENT LIMITATION Custom Field values must be manually maintained across related tasks, creating duplicate work and increasing the risk of inconsistent data. PROPOSED ENHANCEMENT Allow users to map and sync Custom Fields between related tasks, with options for one-way or two-way synchronization. EXAMPLE USE CASE Two tasks are connected through a Relationship: Task #1: Client Name = ABC Company Task #2: Client Name = ABC Company If the Client Name changes on Task #1, the corresponding Custom Field on Task #2 automatically updates. SUGGESTED FUNCTIONALITY • Select which Custom Fields to sync. • Support one-way and two-way synchronization. • Enable syncing across Lists, Folders, and Spaces. BUSINESS VALUE Reduce manual updates, maintain data consistency, and improve cross-team workflows. Note: This request is for actual Custom Field synchronization, not simply displaying values through Relationship Rollups.

Problem Currently, when configuring which fields/columns are displayed in List View, the distinction between "Hide column" and "Delete field" is unclear. From a user's perspective, if I don't want a field displayed in my List View, I would naturally expect to remove it from that view. I wouldn't necessarily think of hiding it as an alternative, especially if I have no intention of showing it again. As a result, clicking "Delete field" can seem like the logical choice. However, deleting a field does much more than remove it from the current view: it permanently deletes the field from the workspace, affecting everyone, and makes it unavailable for future use. There is no clear indication of these consequences before taking the action. UX issues The terminology and placement of "Hide column" and "Delete field" make it easy to confuse view-level actions with workspace-level actions. There is no warning that deleting a field affects the entire workspace and all users, rather than just the current view. There is no confirmation modal before permanently deleting a custom field, making accidental deletion too easy. Managing workspace-level custom fields directly from List View mixes two different levels of configuration and creates unnecessary risk. Suggested improvements My recommendation would be to separate custom field management from List View configuration. Managing, editing and deleting custom fields should happen in a dedicated settings or management area, rather than directly within the List View. At a minimum, however, the following safeguards should be introduced: Clearer distinction between actions: Make it explicit that hiding a column only affects its visibility in the current view, whereas deleting a field removes it from the workspace. Mandatory confirmation modal: Require users to confirm before deleting any custom field, regardless of whether it is a workspace-level or local field. Clear impact warning: The confirmation should explicitly state the scope and consequences of the deletion, particularly when it affects the entire workspace and other users. The current experience makes a potentially destructive, workspace-wide action too easy to trigger by mistake. Custom field management should be designed in a way that makes the scope of an action immediately clear and prevents accidental data loss.

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

Description of the requested improvement We would like to suggest an improvement to how Required Custom Fields work in ClickUp. Currently, Required Custom Fields are enforced when a task is initially created. However, when an existing task is moved from one List to another, the required field validation does not appear to be triggered again based on the destination List. This creates an issue for organizations that manage workflows involving multiple teams and processes. Example of our use case: A task is created in the Support List, where users complete the required fields configured for that process. The task is then moved to the Development List. Development has its own Custom Fields, which are also configured as required. However, ClickUp allows users to leave these fields empty because the task was already created in another List. As a result, users can continue managing the task without completing the information specifically required by the Development process. Our proposed improvement We would like Required Custom Fields to be enforced according to the task's current List, not only according to the List where the task was originally created. Whenever a task is moved to a different List, ClickUp should automatically recognize the required Custom Fields configured in the destination List and require users to complete them. The validation should work regardless of where the task was originally created. Expected behavior: When a task is created, the required fields of its current List must be completed. When the task is moved to another List, the required fields configured for the destination List must also be enforced. Users should not be able to leave these required fields empty and continue saving or updating the task. This validation should work without requiring additional statuses, manual notifications, external integrations, or duplicated tasks. Why this improvement is important Many organizations use ClickUp to manage workflows across different departments, where each team is responsible for completing specific information at different stages of a task's lifecycle. Required Custom Fields should ensure data completeness throughout the entire workflow, rather than only during initial task creation. This improvement would significantly strengthen data integrity, process control, traceability, and the overall reliability of ClickUp as a workflow management platform.

Please give Number Custom Fields more control over how values display, including: Showing or hiding thousands separators (commas). Choosing the number of decimal places, including zero. Preserving leading zeros. We use numbers for purchase orders, customer IDs, and equipment identifiers, not just calculations. An identifier like 9893 should display as 9893, not 9,893 or 9893.00. These options should be saved per field and display consistently across views, forms, and task details, without requiring us to switch to a Text field.

I created a custom field at the workspace level for tracking important information. I'm confident no one deleted it accidentally, but it suddenly disappeared from my workspace. This has caused some disruption, as the field was crucial for our workflow. While I've recreated the field, a feature to prevent accidental deletion of custom fields would be incredibly helpful in the future. It would provide peace of mind and ensure our data remains secure.

Need custom fields included in the Free tier so we can actually put a decent evaluation into place while considering productivity tools. I spent pretty valuable time today spinning up projects, tasks, custom fields so I could see if this tool would work for my company only to hit a paywall before I even was able to do much. I like Clickup, I really do, but after using AI I found several alternatives that dont hide so many features behind a paywall.

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.

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.

Solution and problem We are requesting both preventative features and corrective features: Warning prompt for when a Custom Field is being added to the Everything level Activity Logs to view how and when a Custom Field got added to the Everything level Remove the paywall for the ability to move Custom Fields down the hierarchy to Spaces, Folders, or Lists. At the very least, up until #1 is met! Without these systems in place, you are punishing your inexperienced users for mistakes which cannot be avoided in the current state of ClickUp. You are losing trust [and business!] among users who don't bother speaking up on this matter — as well as those who do! For users who can’t opt out of using ClickUp, you’re causing us to lose time out of our day-to-day routines. Context and elaboration Currently, Custom Fields are inadvertently being added at the Everything level without knowledge of the user, and it is irreversible on the Business plan or below. Upgrading to the Business Plus Plan lets us use a feature to help reverse the mistake. In other words, as it is right now: we need to pay for our mistakes. To be honest, it feels like a set up. For small businesses like mine, these mistakes can be costly, yet they happen without us even being aware. Many of us ClickUp users truly believe that the reversible feature should be available for all users on all plans , especially considering how easy it can be to make the mistake initially. Warning prompts are preventative, they build trust with the user, and they omit the need for unexpecting charges to user accounts. Activity Logs allow us to learn from our mistakes and reflect after the damage has been done. Removing the paywall on the 1 feature that reverses these mistakes altogether saves us time and frustration. Actions known to add fields without prompting Please write in the comments if you've discovered sneaky ways in which Custom Fields get added to the Everything level without your permission. I will try to remember updating the list below with your responses. Moving tasks to a newly-created List using the bulk-action toolbar Moving a filtered View from one Space to another Space Moving a filtered View to the Everything level Adding Columns in Everything View Adding Filters in Everything View ClickUp users speaking up As of November 1, 2023 the Custom Field Manager was marked complete. In the comments, we had our pleads to keep this feature from being paywalled. Let's go round-2 by upvoting this post. Reference URL to the old post: https://feedback.clickup.com/feature-requests/p/move-custom-fields-between-spaces-folders-and-lists Related posts worth upvoting: Add Columns in Everything View without adding custom field on the Everything View https://clickup.canny.io/feature-requests/p/add-columns-in-everything-view-without-adding-custom-field-on-the-everything-vie Add filter on custom fields at the Space or Everything level without adding the custom field to that level https://clickup.canny.io/feature-requests/p/add-filter-on-custom-fields-at-the-space-or-everything-level-without-adding-the See activity for deleted items in Activity view https://feedback.clickup.com/feature-requests/p/see-activity-for-deleted-items-in-activity-view Prompt to fill in field values when task is being moved to a location with a required Custom Field https://clickup.canny.io/feature-requests/p/prompt-to-fill-in-field-values-when-task-is-being-moved-to-a-location-with-a-req