Field Limits & Management
Custom field limits and how custom fields are configured across the settings pages.
Field Limits
Custom fields have a couple of limits designed to keep projects manageable and prevent data quality issues. Understanding these limits helps you plan your custom field strategy before creating fields.
| Limit | Value | Details |
|---|---|---|
| Fields per project | 10 | Each project can have a maximum of 10 custom fields. The 11th is refused with cannot create more than 10 custom fields. |
| Field name length | 25 characters | The create form accepts up to 25 characters. Keep names concise. |
| Field name uniqueness | Per project | Two custom fields in the same project cannot share a name, and the comparison ignores case — Browser and browser collide, and the second is refused with Custom field with same name already exists. |
| Selectable field types | 5 | TEXT, NUMBER, CALENDAR, SINGLE_LIST and MULTI_LIST. |
The 10-field limit is per project, and it counts every custom field in the project — including fields you have hidden on Field Configuration. Hiding a field does not free a slot; only deleting it does, and deleting is permanent.
If your project already has 10 custom fields and you need to add another, you must delete an existing field first. Consider consolidating related fields (e.g., use a single MULTI_LIST instead of multiple SINGLE_LIST fields) to stay within the limit.
Plan your custom fields before creating them. Since the 10-field limit is per project, think about which metadata is most valuable for your team's workflow. Note that a field's type and name cannot be changed after creation — to change either, delete the field and create a new one.
Managing Fields
Custom field configuration is spread across three settings pages:
| Where | What you configure |
|---|---|
| Settings → Custom Fields | Create a field (name + type) and delete it. Fields are listed in the order they were created. |
| Settings → Field Value | The options a SINGLE_LIST or MULTI_LIST custom field offers. |
| Settings → Field Configuration | The Mandatory and Visibility toggles for the field. |
Mandatory and visibility toggles
Custom fields appear on the Field Configuration page alongside the built-in fields, each with a Mandatory and a Visibility toggle.
- Turning Mandatory on means a test case cannot be saved until the field has a value. It also forces Visibility on and locks that toggle — a mandatory field cannot be hidden.
- Turning Visibility off removes the field from test case forms, the detail view, filters and the import template. Existing values are preserved and reappear if you turn it back on.
Not available for custom fields: default values, renaming an existing field, changing its type, and drag-and-drop reordering. The Custom Fields page supports create and delete only — to change a field's name or type, delete it and create a new one.