Feature Requests

Situation: Currently, there is no option to add a formula (custom field) to different locations (lists e.g.). The only way is to dublicate the formula in the new location. Solution: Formula custom fields should be allowed to be added to different locations in the custom field manager.

I think a confirmation prompt after editing in the main "Edit Field" view is plenty of guardrail. Hiding something simple such as "Edit Field Type" behind advanced settings, especially when you still choose to show a grayed out "Edit Field Type" on the main UI feels really high friction for a fairly simple task.

Description: Currently, ClickUp’s formula custom fields can only access the total time tracked on a task, with no ability to filter or sum time entries by date or date range. This limits reporting and automation capabilities, especially for organizations that need to analyze or display time tracked within specific periods (such as the current calendar month, week, or quarter) directly in task views or dashboards. Requested Enhancement: Allow formula custom fields (including AI-powered formulas) to reference individual time entries, not just the total. Introduce formula functions or AI logic that can sum or filter time tracked based on a specified date range (e.g., only time tracked in the current month). Enable dynamic date filtering using functions like THIS_MONTH(), LAST_MONTH(), or custom date ranges within formulas. Ensure these enhanced formulas can be used in List/Table views, dashboards, and reporting widgets. Benefits: Enables more granular and automated time reporting directly in ClickUp. Supports common business needs such as monthly timesheets, project billing, and performance tracking. Reduces the need for external exports or manual calculations. Leverages ClickUp’s AI and formula capabilities for smarter, more flexible reporting. Example Use Case: A formula custom field that displays “Total Time Tracked This Month” for each task, automatically updating as new time entries are logged. Suggested Formula Syntax Example: SUM_TIME_TRACKED_IN_RANGE(start_date, end_date) or TIME_TRACKED_THIS_MONTH() Summary: This enhancement would make ClickUp’s time tracking and reporting much more powerful and flexible, especially for teams that rely on accurate, period-based time data.

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.

I would love for the ability to use custom emojis when creating custom fields. This way, I can create workspace level fields and indicate them as such with our company Emoji (vs using a "star" or "globe" or some other generic emoji

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.

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.

I send emails to nonmembers and guest all of the time to track conversations with potential and current clients. It would be awesome to separate multiple emails by a comma or semicolon. I often have a team client as a task and there are multiple parties on each communication or a communications email and a billing email. Additional emails currently have to be stored in other fields or multiple unnecessary email fields take up space in other tasks that don't need them.

I have created many custom fields. It would be great if we can rearrange the custom fields so it will display as we wanted to in the task As you can see in bullet 1, 2, and 3, I have arranged the fields in order Approval Complete Status. But right now, all those fields don't display as order as I wanted, you can see Bullet A, B, and C so you know what I mean