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.