Feature Requests

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.

Kindly find the attached picture. Text in Yellow is not readable in it's current state. Similar things happen a lot in our workspaces where we force to read what is written in a field. Please make necessary changes

We use specific custom fields for our organisation, e.g. dropdown to evaluate the budget status. I put a description under the custom field for e.g. on track, needs attention, at risk. When we apply the custom field as a column. When we hover over the custom field, the description pops us with ....more when the text is longer than the display. We face the issue that the description of the custom field fades out quickly and people cannot read it - meaning they don't understand the definition of the value in this field. It would help us a lot if the pop up faded out slower to give users time to read the description.

We are using a custom field called Category to categorize type of work for tasks/tickets. We'd like to implement a subcategory field that can dynamically populate values based on what the value of Category is. Is this a possibility in the near-future?

Ability to have conditional logic for all custom fields. Es. if custom field X is active, it automatically activates (and displays) field Y avoiding useless custom fields in specific tasks

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.

A Custom Field pop up coming up prompting the user to fill in details of a custom field or multiple custom fields when status changes. This will be a great addition to several workflows especially when using Mobile. It will reduce the time spent scrolling sideways to look for the field to fill in.

A custom field identical to a dropdown menu but with 2 dimensions. An N-column table where the choices of N+1 depend on the choice of N.