Feature Requests

FEATURE REQUEST Allow tasks connected through a Relationship to automatically sync selected Custom Fields. CURRENT LIMITATION Custom Field values must be manually maintained across related tasks, creating duplicate work and increasing the risk of inconsistent data. PROPOSED ENHANCEMENT Allow users to map and sync Custom Fields between related tasks, with options for one-way or two-way synchronization. EXAMPLE USE CASE Two tasks are connected through a Relationship: Task #1: Client Name = ABC Company Task #2: Client Name = ABC Company If the Client Name changes on Task #1, the corresponding Custom Field on Task #2 automatically updates. SUGGESTED FUNCTIONALITY • Select which Custom Fields to sync. • Support one-way and two-way synchronization. • Enable syncing across Lists, Folders, and Spaces. BUSINESS VALUE Reduce manual updates, maintain data consistency, and improve cross-team workflows. Note: This request is for actual Custom Field synchronization, not simply displaying values through Relationship Rollups.

Do not collabse Label custom field if it not necessary. Like on the picture - I can see them all - there is enough space.

Need custom fields included in the Free tier so we can actually put a decent evaluation into place while considering productivity tools. I spent pretty valuable time today spinning up projects, tasks, custom fields so I could see if this tool would work for my company only to hit a paywall before I even was able to do much. I like Clickup, I really do, but after using AI I found several alternatives that dont hide so many features behind a paywall.

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

Problem: When using Tasks in Multiple Lists to share tasks across different audiences (e.g., an internal engineering list and an external client-facing list), all Custom Fields from the task's Home List are visible when opening the task detail, regardless of which list the viewer is accessing it from. There is no way to hide specific fields per view or per list context. This creates an information leak: internal fields like "Complexity," "Internal Cost," or "Engineering Notes" are fully visible to external stakeholders (clients, partners) who access the task from a client-facing list. The only workaround today is to not use multi-listing at all and duplicate tasks manually, which defeats the purpose of the feature. Use case: We are a managed services company that uses ClickUp to run projects. Our internal engineering team works from one Space with detailed operational fields. We share project progress with clients through separate lists in a client-facing Space. Multi-listing is the natural solution, but because we cannot control field visibility per context, we are forced to either expose internal data to clients or abandon multi-listing entirely. Proposed solution: Allow Workspace admins or view creators to configure which Custom Fields are visible in the task detail panel on a per-view or per-list basis. When a user opens a task from a specific list/view, only the fields enabled for that context should appear in the detail panel, not just in the column headers. Impact: Without this, Tasks in Multiple Lists loses its value for any organization that needs audience separation (internal vs. external, team A vs. team B). This is a common need for agencies, consultancies, and IT service providers who share project visibility with clients inside ClickUp.

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.

Click up automatically assigns colours a drop down options. I appreciate we can change the colours manually but we need to be able to bulk change a certain number of drop options to a matching colour to help with visual categorisation.

We have a large team with multiple spaces. We work to streamline our process by limiting new custom fields, this way there are not several overlapping fields in different spaces that do practically the same thing. However, managing this becomes difficult. When a team wants to add new fields we have to communicate outside of Click Up and it becomes cumbersome trying to figure out if they need the new field or can use something existing. This slows down production. It would be very beneficial to have an approval system for custom fields where Members can request a new Custom Field, then Admins can determine if the new field is necessary or not and can approve or send back a note with the existing Custom field to use.

I would like to request the ability to create custom fields that are unique to a specific Space within ClickUp, rather than having them available across the entire Workspace. This feature would greatly enhance our ability to organize and manage data more effectively, reducing clutter and improving workflow efficiency. It feels like a basic functionality that would benefit many users. Thank you for considering this request!

Add a system level setting to default Custom Field Guest Visibility to Off. Currently, all new fields are set so that guests can see them by default and this is risky that you create a new sensitive data field and forget to check/change it to off. It would always be better to have it the other way around where you realize that the field is not visible and knowingly choose to turn it on.