Feature Requests

Request: Please expose the “Email to this task” address as a task field that can be shown in views and referenced like Task ID. Ideally it would be available as: A built-in column/field (similar to Task ID), and/or A Custom Field value that can be added to Lists and used in Automations, templates, and exports. Why: Many teams route external emails into ClickUp and need the per-task email address visible for quick copy/paste, documentation, and integrations, without opening the task menu each time. Notes/constraints: If the email address is user-specific, it would still be useful to expose “my email-to-task address” for the task, and optionally a workspace setting to expose a shared canonical address if available.

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.

For now the Progress Bar (Auto) is not going to be updated, when I have subtasks in subtasks, which are marked as done. If the first level of subtasks are not done but every subtasks under it, the filed is still at 0%.

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

The ability to change a text area into a shorter text area.

Not being able to use ClickUp's flexibility with the new AI tools is very off-putting. We need to be able to create a space, the list(s), all custom fields and their data/dropdowns, AND have the columns showing in the list via MCP, API, or both. But this is INCREDIBLY hampering not being able to say to Claude, "create these custom fields for me and show them in the list". The fact that Brain can't do this either... Seems like a $4 billion org should be able to scrape this stuff together? and fairly quick? You guys are clearly aware of the AI changes happening, but if you don't allow the flexibility, people will move to Airtable/Jira or an entirely new app that exposes all the endpoints the user might want. I do not want to click through the UI for this stuff anymore. No one does. The entire world is going to expect to be able to natural language any shape on any platform into existence. If you need to roll out some permissions or whatever, warnings, fine. Some of us are happy to allow the AI to do the heavy lifting. Please, offer some feeback or updates around these plans.

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.

Custom Fields for Task Types are great but one of the main reasons I would use them is to filter out formulas on tasks in a single list. Because Formula fields are not able to be a Custom Task Type Field it defeats 80% of the use cases I have for Task Type Custom Fields.

I would like to be able to restrict the creation and deletion of task based custom fields to administrators but allow greater flexibility for super users to create custom fields on lists to support their projects. Currently the non admin users that can create / delete fields can also do that on task type fields putting at risk the setup of the system across multiple teams.

Summary / Why we’re requesting this We are a law firm using ClickUp to manage matter workflows across multiple practice areas. Our workflow requires filling out Custom Fields progressively as a matter moves through stages. For our team to work efficiently and avoid missing key information, we need the Custom Field section on a task to remain in a consistent, predictable order throughout the life of the matter. Right now, Custom Fields rearrange themselves automatically based on filled vs empty, and also get reshuffled during stage changes and template application. This is not just cosmetic; it breaks our ability to quickly confirm what is done vs missing and creates real operational risk. Our setup (real example)In one practice area, a single matter task includes 18 Custom Fields, in a specific order we rely on, including: • Stage field • Plan Type field • Plan Price field • Notes field • 2 AI fields (Next Due, Next Steps) • 8 custom date fields that are filled in as we progress (initial consultation, meeting dates, drafting dates, engagement dates, signing dates, etc.) • A client intake vault link field (URL) • Phone field • 2 email fields We are setting up five practice areas with different sets of Custom Fields [the example above is just for ONE area] (some reused CF across practice areas). Standardizing and locking field order becomes even more important at this scale. What’s happening now (problem details)–We pin our fields, but the order still changes repeatedly due to system behavior such as: Filled vs empty sorting: As we populate date fields over time, fields shift from “empty pinned” to “filled pinned,” which changes the order and forces users to hunt for fields. Stage changes: We have several stages per practice area. The main matter task functions as the “home” for the overall project and houses the stage progression, while stage changes can generate related tasks/subtasks. When we change stages, the custom fields rearrange due to how field display/hierarchy behaves. Templates: Applying templates during stage changes does not preserve Custom Field display order, so the layout resets or reshuffles again. Actual vs Expected Actual: • Pinned Custom Fields move around when they change from empty to filled. • Stage changes and applying templates can reset or reorder the Custom Field layout. • Result: the Custom Field section “shuffles” throughout the matter lifecycle, which is disruptive and increases the risk of missing key dates and client info. Expected: • Add a “LOCK” option to lock Custom Field display order in tasks so fields stay exactly in the sequence we set. • The locked order should ignore filled/empty sorting (filled fields should not jump to a different section/order). • Stage changes and template application should not change the locked Custom Field order. • Ideally: templates should be able to save/restore field display order, or the lock setting should override any template-driven reordering. Impact We rely on these fields as a live checklist of matter progress. If the order is stable, a user can open the task and instantly see what dates/details are complete vs missing. When the order continually changes, it slows work, creates confusion, and makes ClickUp difficult to use for our practice-area workflows.