Feature Requests

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.

The same Customs field could be used in different contexts. More precisely, the set of potential values of a dropdown field could be used with two different meaning. It could be interesting to provide different name (and different description) for the Column (within a given view) than the name of the custom field taht contains teh dropdown option (and any Custom field type that contains many options).

Sometimes we use custom fields really often, and maybe there are tasks that have a large description, so it makes not so easy to reach a custom field in the bottom of a task (even though it's pinned). It would be truly helpful to be able to place a custom field in the upper-left section, or the header of a task.

Currently. when creating custom fields that are required in a list/folder/space, when setting a relationship field as required, it creates the requirement in the other side as well. When enabling 'Required in tasks' on one side of the relationship, the other side is also required. For instance. I have a Contacts and Customers lists. I also have a billing list. When creating tasks on the billing list, I want to be able to require a contact task and customer task to create the billing task, BUT, when creating a new contact task or customer task, I don't want to also have to add a billing task because this customer doesn't have any billing tasks yet. It would be very nice to be able to create a one-way specific relationship requirement in a list that only affects that list and not the related tasks.

I have a promotion that I'd like to run for a product. I want to have a Date Range field, so I can easily see in the calendar when the promotion is running. I'd also like to use the Due Date field for the date I must finalize the promotion by. Currently I'm using two Custom Date Fields ("Begin Date" and "End Date", as using Start Date affects the Due Date field) and they only appear in the calendar on the dates specified, rather than spanning that measure of time. I think being able to visualize the range of time in the Calendar would be extremely useful, as I would be able to see more easily if two promotions might overlap.

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.

It would be great if we could assign custom fields to custom groups - essentially 'tagging' fields to a specific category (and sub-categories) and then being able to filter on those categories when viewing the custom fields. For example, we might have 25 custom fields for our 'project management' workflow, and 17 fields for our 'CRM' workflow. When adding a custom field to a new list on the project management side, I want to be able to filter the existing custom fields on the 'project management' category, and not have the visual clutter and confusion of also seeing the 17 'CRM' custom fields. Basically, add a 'Category' column as per attached screenshot and make that column part of a filter in the 'Add Property' functionality of a list.

ClickUp really needs the ability to allow users to remove custom fields from locations in bulk. Removing many custom fields from a location is incredibly time-consuming.

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

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.