Field Configuration
Custom field limits and how field management works today.
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. |
| Field name length | 30 characters | The field name (label) can be up to 30 characters. Keep names concise. |
| Selectable field types | 2 | The create form offers SINGLE_LIST and MULTI_LIST today. |
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 Today
After creating custom fields, you manage them from the Settings → Custom Fields page. This page lists all custom fields in the project with their name and type, in the order they were created. From here you can create new fields and delete existing ones.
🚧 Coming soon — richer field configuration is planned but not available yet:
- Default values — pre-filling a field's value on new test cases.
- Editing / renaming an existing field or changing its options.
- Drag-and-drop reordering of fields.
- Enable/disable and mandatory toggles.
Today, custom fields support create and delete only. To change a field, delete it and recreate it.