Session Templates
Session Templates control the field layout shown when creating a test session. They work the same as Repository Templates but apply to Session Fields instead of Case Fields.
Key differences from Repository Templates
| Repository Templates | Session Templates | |
|---|---|---|
| Applies to | Test cases | Test sessions |
| Tab | REPOSITORY | SESSIONS |
| Fields used | Case Fields | Session Fields |
| STEPS type | Supported (Case Fields only) | Not supported (Session Fields exclude STEPS) |
| Deletion impact | Cases reassigned to default template | Sessions reassigned to default template |
STEPS fields are not available in session templates. Session Fields do not include the STEPS type. If a field was defined as STEPS in the Fields module, it will not appear as an option when adding fields to a Session Template.
The template list
The SESSIONS tab in Admin → Templates displays all session templates with the same columns as repository templates: Name, Projects, Enabled, Default, and Actions (Edit, Delete).
The default template
Every workspace has exactly one default session template. It is auto-selected when a user opens the Create Session form, cannot be deleted, and is always enabled. To change the default, set another enabled template as default first.
How templates work with fields
Session templates reference Session Field definitions from Admin → Fields → Session Fields. When you add a field to a session template, you configure:
| Configuration | What it does | Applies to |
|---|---|---|
| Required | Whether the field must be filled before the session can be saved | All field types |
| Default Value | Pre-populated value shown to the user when the template loads | All field types |
| Options | Override the global option list with a template-specific list | DROPDOWN, MULTI_SELECT |
Fields in a session template are displayed alphabetically. There is no drag-and-drop reordering.
Project assignment
Session templates support the same project assignment as repository templates — All Projects (default) or Selected Projects. The default session template is always available in every project regardless of assignment.
Create a session template
- Click New Template on the SESSIONS tab.
- Enter a Name for the template.
- On the TEMPLATE tab, add fields by selecting from the workspace's Session Fields. For each field, configure its required state, default value, and any option overrides.
- On the PROJECTS tab, choose All Projects or select specific projects.
- Click Save.
Enable and disable
Toggle the Enabled switch on the template row. Disabled session templates show as "(Unavailable)" in the session creation form. Existing sessions using a disabled template are unaffected — the template is only unavailable for new sessions. Re-enabling restores availability immediately with no data loss.
Prefer disabling over deleting. A disabled template preserves all existing session data and can be re-enabled at any time.
Delete a session template
Deleting a session template is permanent. All sessions using it are reassigned to the default session template, and field values for fields not included in the default template will be permanently lost.
Deletion causes data loss. Deleting a session template reassigns all its sessions to the default template. Any field values for fields not present in the default template will be permanently deleted. Consider disabling the template instead.
The default session template cannot be deleted. Set another template as default first.