Feature Requests

Please search first before posting to help others find and vote for your idea!
Prevent accidental deletion of custom fields from List View
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.
0
·
Custom Field Manager
Feature Request: Enforce Required Custom Fields When Moving Tasks Between Lists
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.
0
·
Custom Field Manager
Load More
→