Feature Requests

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.

Ability to show/hide custom fields based on the value of other custom fields. A simple option to "Show if" condition when creating new custom fields.

At a minimum, a changelog for custom fields would be great. Being able to see who changed what and when. Being able to comment/discuss in the same manner as a task seems like it'd be beneficial. So basically the Activity section from a task but for custom fields. This would be useful for my teams.

Convert Labels to Dropdowns. We can do it the other way in 3.0, but we need to be able to convert a Label into a Dropdown Menu.

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

As you all know, ClickUp is an extremely powerful, versatile tool with a multitude of uses. Thanks to custom fields, we can build a tool tailored to the needs of many usage environments: sales, purchasing, administration, production, development, help desk, etc. Another great feature of ClickUp is collaboration and teamwork. Thanks to this, teams from all sectors can work together under the umbrella of a unified platform. The problem arises when it is necessary to fill in a custom field in order to CLOSE the task. Currently, ClickUp allows requiring the completion of one or more custom fields to create a task. This is very good and extremely useful. But what happens when we want the opposite? That is, to ensure that information is entered in a custom field or fields in order to close a task correctly? It may be that these custom fields are not required at the beginning when we create the task, but they should be required to complete the task. It would be very interesting for ClickUp to add the option of mandatory fields to complete a task. Imagine a scenario in a help desk environment. When creating the task, there is a custom text field that will include the ticket solution or incident resolution, and the text entered in this field will be automatically sent in our closure email. Obviously, this field cannot be mandatory when creating the task because we have not yet resolved the incident and therefore do not know what resolution description to include in this field. However, if it is not mandatory to close the task, what happens if we close a task with this field left blank? The ticket closure email will be sent without a resolution description, and we will appear unprofessional to our client. For this reason, in this use case, I think it would be a good idea for the custom text field "Ticket Solution" to be mandatory to close the ticket and for the task not to be closed without this field being properly filled out. What do you think? There are many more use cases... one that comes to mind is a checkbox field to confirm that the user has reviewed a procedure, and if the checkbox is not marked, the task cannot be closed. I look forward to your comments and votes.

Is it possible to divide the fields into sections, for example profile, business, resources, etc. (custom) and sort them in the desired order - we use them as a questionnaire and it would be great to have such an option

It would be great if we could set default Custom Field values on a per-List basis instead of globally. Globally has been released ( https://feedback.clickup.com/feature-requests/p/set-default-value-for-custom-fields ), but per-List would be great!

It would be extraordinarily helpful to see when a custom field was last updated. For example, I monitor changes to custom fields on a weekly basis. This is a manual process, where I have to review each field individually and spot changes. Knowing which fields have been updated when would make this task much easier.

It would be helpful to have the CF Manager allow you to group by location when looking at All Custom Fields.