Session Fields
The SESSIONS tab in Admin → Fields manages fields for test sessions. Session fields capture structured metadata when a session is created — things like the testing environment, session goal, or device under test.
How Session Fields differ from Repository Fields
| Repository Fields | Session Fields | |
|---|---|---|
| Applies to | Test cases and test results | Test sessions |
| Admin tab | REPOSITORY | SESSIONS |
| Sub-categories | Case Fields and Result Fields | Single category (session fields only) |
| STEPS type | Supported | Not supported |
| Template usage | Case templates | Session templates |
Create a session field
- Go to Admin → Fields → SESSIONS and click New Field.
- Enter a Label. The System Name is auto-generated from the label — you can edit it before saving.
- Select a Type. All types except STEPS are available. See Field Types.
- For DROPDOWN or MULTI_SELECT fields, add the options users can choose from.
- Set whether the field applies to All Projects or Selected Projects.
- Click Save.
System Name rules: Must be lowercase, may contain underscores, must start with a letter. System Name is permanent and cannot be changed after the field is created.
Edit a session field
Click the Edit button on a field row. You can change:
- Label
- Enabled state
- Project assignment scope (All Projects or Selected Projects)
- Options (for DROPDOWN and MULTI_SELECT fields)
Field type and System Name cannot be changed after creation.
Enable and disable a session field
Toggle the Enabled switch on the list directly. Disabling a field hides it from new session creation but preserves all previously stored values.
Delete a session field
Click the Delete button on the field row and confirm the dialog.
Deletion is permanent. Deleting a session field removes all values stored for that field across every project and session. This cannot be undone. Disable the field instead if you want to preserve historical data.
Project Overrides
Click the Overrides button on a field row to configure project-specific behaviour — required state, default value, and option restrictions.
For full detail, see Project Overrides.
"Can I use the same field for both cases and sessions?" No — Repository fields and Session fields are separate. If you need the same data captured in both contexts, create two fields: one under REPOSITORY and one under SESSIONS.