Field Types
When creating a field you choose a type. The type determines the input control shown to users and the kind of data it stores. Field type cannot be changed after the field is created.
Field type is permanent. Once a field is saved, its type cannot be changed. Choose carefully — changing a field type would corrupt existing stored values.
Available types
| Type | Input shown to users | Available for |
|---|---|---|
| TEXT | Single-line text input | Case, Result, Session |
| STRING | Multi-line text area | Case, Result, Session |
| INTEGER | Whole number input | Case, Result, Session |
| FLOAT | Decimal number input | Case, Result, Session |
| DATE | Date picker | Case, Result, Session |
| CHECKBOX | Boolean toggle (on/off) | Case, Result, Session |
| LINK | URL / hyperlink input | Case, Result, Session |
| DROPDOWN | Single-select from a list of options | Case, Result, Session |
| MULTI_SELECT | Multiple selections from a list of options | Case, Result, Session |
| STEPS | Step-by-step structured input with subfield slots | Case only |
DROPDOWN and MULTI_SELECT options
When creating a DROPDOWN or MULTI_SELECT field, you define the list of options that users can choose from.
- Up to 50 options per field
- Each option has a value (unique internal identifier) and a label (displayed to users)
- Options can be individually enabled or disabled — disabling an option hides it from new selections but preserves it in existing data
- The global option list can be replaced on a per-project basis using Project Overrides
STEPS field
The STEPS type creates a structured, multi-column input — typically used to capture test steps, expected results, actual results, and notes. It is only available for Case Fields — it cannot be used for Result Fields or Session Fields.
A STEPS field has 4 fixed subfield slots. At the workspace level, these slots have default labels. Each project can customise the slots independently using Project Overrides:
- Rename a slot label
- Enable or disable individual slots
- Reorder the slots
STEPS subfield customisation is per-project. Subfield slot names and order are configured in the project override for each field — not at the global field level. This means different projects can use the same STEPS field with different column labels.