Feature Requests

Please search first before posting to help others find and vote for your idea!
Enable Workspace-Level Custom Fields and Custom Field Manager for CRM Setup
I am in the process of building a CRM and regulatory compliance management system for my business using ClickUp. I have encountered an issue where custom fields created in one Space are not consistently available across other Spaces, Folders, and Lists. In addition, I am unable to access a dedicated Custom Field Manager to centrally manage, reuse, and deploy custom fields throughout my workspace. My workflow requires a centralized CRM structure with linked client records, application tracking, follow-ups, reporting, dashboards, automations, and relationships. To achieve this, I need the ability to: Create and manage custom fields at the Workspace level. Reuse existing custom fields across multiple Spaces, Folders, and Lists. Access a central Custom Field Manager to view, edit, organize, and deploy all custom fields. Create relationship fields between client records and application records. Use rollups and reporting based on those relationships. Maintain consistent custom fields across the entire workspace without recreating them for each location. Examples of fields required include: Client Name Contact Person Company Registration Number VAT Number Application Type Lead Source Service Fee Submission Date Approval Date Next Action Next Action Due Date Client Rating Relationship Fields and Rollups Could you please advise: Whether Workspace-level Custom Fields and the Custom Field Manager are available on my current plan. Whether these features can be enabled for my workspace. Which subscription tier is required to access these capabilities if they are not currently included. These features are critical for building a scalable CRM and compliance management system within ClickUp.
0
·
Custom Field Manager
Allow Number Custom Fields to Display Without Thousands Separators (Commas)
Currently, ClickUp automatically formats Number custom fields with thousands separators (commas). While this formatting is useful for many use cases, there are situations where commas are unnecessary or create visual inconsistencies, particularly when the field is being used for identifiers, reference numbers, job numbers, project codes, invoice numbers, or other non-financial values. It would be extremely helpful to provide a formatting option that allows administrators to choose whether a Number custom field displays with or without thousands separators. Example: * Current: 12,345 * Desired Option: 12345 Benefits: * Improves flexibility of Number custom fields across different use cases * Better supports project IDs, job numbers, invoice references, and tracking numbers * Creates consistency with external systems that do not use comma formatting * Reduces confusion when numerical values are intended as identifiers rather than quantities or currency * Improves reporting, exports, and visual presentation of operational data Ideally, this would be a field-level setting that allows Workspace Administrators to select whether thousands separators are displayed, rather than applying a single formatting standard across all Number custom fields. This enhancement would make Number custom fields significantly more versatile for operational, financial, project management, and reporting workflows.
1
·
Custom Field Manager
Load More