Field Configuration
Configure field limits, defaults, ordering, and enable/disable fields.
Field Limits
Custom fields have several limits designed to keep test case forms manageable, ensure consistent performance, 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. This limit ensures test case forms remain readable and performant. |
| Field name length | 100 characters | The field name (label) can be up to 100 characters. Keep names concise for better form readability. |
| TEXT field value | 500 characters | The maximum length for a TEXT field value entered on a test case. |
| List options per field | 50 | Each SINGLE_LIST or MULTI_LIST field can have up to 50 options. |
| Option label length | 100 characters | Each option in a list field can be up to 100 characters long. |
| NUMBER field range | Standard numeric range | Accepts integers and decimals. Extremely large or small values may be rounded for display. |
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. You can always add more fields later if you have not reached the limit, but changing a field type requires deletion and recreation.
Field Defaults
Default values save your team time by pre-populating custom fields on new test cases. When a default is set, every new test case created in the project will have that field automatically filled in with the default value. Users can always override the default during creation or when editing a test case.
How Defaults Work by Field Type
- TEXT — The default is a text string that pre-fills the input. Example: set "Sprint 1" as the default for a "Sprint" field.
- SINGLE_LIST — The default is one of the predefined options, pre-selected in the dropdown. Example: set "Chrome" as the default for a "Browser" field.
- MULTI_LIST — The default can be one or more of the predefined options, pre-selected in the multi-select. Example: set "Windows" and "macOS" as defaults for a "Platforms" field.
- CALENDAR — The default is a specific date pre-filled in the date picker. Note that a fixed default date may become stale over time.
- NUMBER — The default is a numeric value pre-filled in the input. Example: set "3" as the default for a "Story Points" field.
Setting and Changing Defaults
You can set a default value when creating the field, or add or change it later:
- Navigate to Settings → Custom Fields.
- Find the field you want to update and click the Edit (pencil) icon.
- In the edit modal, set or change the Default Value.
- Click Save. The new default applies to test cases created after this change.
Changing a default value only affects new test cases created after the change. Existing test cases retain their current values and are not retroactively updated.
Use defaults strategically to reduce repetitive data entry. If 80% of your test cases target Chrome, set Chrome as the default for your Browser field. Testers only need to change it for the remaining 20%.
Field Configuration
After creating custom fields, you can manage them from the Settings → Custom Fields page. This page shows all custom fields in the project with their type, options (for list types), and default value.
Reordering Fields
The order of custom fields on this settings page determines the order they appear on test case forms. To change the display order:
- Hover over the field row to reveal the drag handle on the left side.
- Click and drag the field to the desired position.
- Release to drop it in place. The new order is saved automatically.
For example, if you want "Browser" to appear before "Sprint" on the test case form, drag the Browser field above the Sprint field in the list.
Editing Field Properties
Click the Edit icon on a field row to open the edit modal. You can change:
- Field Name — Rename the field. The new name is reflected everywhere immediately.
- Default Value — Set, change, or clear the default value.
- List Options (SINGLE_LIST and MULTI_LIST only) — Add new options, remove existing options, or rename options. See the important note below about removing options.
Removing an option from a SINGLE_LIST or MULTI_LIST field does not retroactively clear that value from existing test cases that already have it selected. However, the removed option will no longer appear in the dropdown for future selections.
Enabling and Disabling Fields
You can enable or disable a custom field to control whether it appears on test case forms. A disabled field is hidden from the creation and editing forms but its data is preserved. This is useful when you temporarily do not need a field but want to keep the historical data.
- Navigate to Settings → Custom Fields.
- Toggle the Enabled switch on the field row.
- When disabled, the field will not appear on test case forms but existing values are retained.
- Re-enable the field at any time to restore it to forms with all data intact.
Disabling a field is a non-destructive alternative to deleting it. If you are unsure whether you still need a field, disable it first. You can always re-enable it or delete it later.