Feature Requests

I use ClickUp every day for my work, and one of the features I find most useful is the “Custom Fields.” They add great flexibility to task and project management, which I truly appreciate. However, during long-term use, there are situations where multiple team members create similar custom fields. For example, we ended up with both a field named “Due Date” and another called “Deadline,” which required us to enter the same information in two places. In another case, we had both “Department” and “Team Division” as separate fields, which caused confusion about which one should be used. In such cases, the current solution requires manually moving information from one field to another for each task, which reduces efficiency. Therefore, having a feature that allows us to merge custom fields would be extremely helpful. For instance, if Field A and Field B could be merged and all existing data automatically migrated into a unified field, it would greatly improve workflow efficiency and maintain data consistency. ClickUp is an amazing service that continues to evolve with the users’ perspective in mind. I am truly grateful to the development team for always listening to user requests like this.

I would love to use ClickUp for more workflows but the one feature that blocks this is limiting access to a specific custom field. What we want to do is allow only limited people to access the approval option for a request. We use a combo box to track progress and would need to have a custom field that only a designated person could update.

It would be great to be able to format text (such as bold, italics, or bullet points) in Custom Field descriptions so that the text is easier to read.

For now, we have to manually insert all holidays to be excluded from the NETWORKDAYS calculations

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.

The objective is to make a custom field mandatory when a task status is Closed. Many of our developers mark tasks as 'Closed' yet don't put any notes on the task to indicate what was done, where it was done, what was deployed to production, etc. It becomes a guessing game if the developer is out and others have to pick up the slack. I've seen several posts about mandatory fields but haven't found one yet that indicates the ability to make a field mandatory when status is changed to closed. Any thoughts on this or am I missing something. Thanks in advance for your help.

It would be interesting to be able to rearrange the custom fields of a task or lists, so that they do not follow the alphabetical order pattern proposed by the click up. I would like me to determine my order to be filled in the custom fields!

I have some constants that I would like to be available globally, especially for calculated fields. Use case example. We tracks some expenses, subscriptions etc in CLickUp. Not all are billed in local currancy, some are in USD. So I want to have an exchange rate variable that can be set somewhere and then be used in calculations. Example Local Currency Amount = field("USD Amount") * constant("USD ZAR Exchange Rate")

It would be super helpful to have custom field data validation options. For example - I need to collect routing numbers that are exactly 9 digits long, or EIN's that are 9 digits long in a format of XX-XXXXXXX. When someone enters something other than that format it should give them an error message. Excel, and other Task management software have this feature, especially for Form Fields that will be submitted by a number of untrained users. Simply giving them a text field to put in whatever they want gets bad data that constantly has to be cleaned up.

I'd want an option to add custom fields to the task itself and not the subtasks within that particular task. Or at least have an option to hide the custom fields section when not needed.