Templates
Templates define the field layout for test cases and test sessions. When a user creates a case or session, they select a template — it determines which fields appear, what values are pre-filled, and which fields must be completed before saving. Admins define templates in Admin → Templates.
Why templates matter
Without templates, every test case would use the same global field configuration. Templates let you define different field sets for different kinds of work. For example:
- A Bug Report template might require a Severity and Root Cause field
- A Smoke Test template might only show Priority and Environment
- A Regression template might include a detailed Steps field with custom column labels
Each project can be restricted to only the templates that are relevant to it. Users select from the available templates when creating a case or session — they see only the fields the admin has configured for that template.
Who can manage templates?
The Templates page is accessible to Tenant Admins and Project Admins.
| Action | Required Access |
|---|---|
| View the Templates page | Tenant Admin, Project Admin |
| Create a template | Tenant Admin, Project Admin |
| Edit a template | Tenant Admin, Project Admin |
| Delete a template | Tenant Admin, Project Admin |
| Set the default template | Tenant Admin, Project Admin |
Two types of templates
Templates are split into two types, each managed on a separate tab in Admin → Templates:
- Repository Templates
- Used when creating and editing test cases. Managed on the REPOSITORY tab. Draw from Case Fields defined in Admin → Fields.
- Session Templates
- Used when creating test sessions. Managed on the SESSIONS tab. Draw from Session Fields defined in Admin → Fields. The STEPS field type is not available for session fields and therefore not available in session templates.
What users see. When a user creates a test case or session, they see a Template dropdown. The default template is pre-selected. Switching templates reloads the visible fields immediately. The template determines which fields appear and which are required — users cannot add or remove fields; that is admin-only configuration.