Templates
Templates define the field layout for test cases and explorations. When a user creates a case or exploration, 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 Settings → Templates.
Why templates matter
Without templates, every test case would use the same global field environment. 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 exploration — 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 on its own tab in Settings → Templates. The page carries the tab in its address, so a link to one context reopens on that context:
- Test case templates
- Used when creating and editing test cases, and when recording a result on one. A test case template draws from two field pools — test case fields and test run fields — both defined in Settings → Fields.
- Exploration templates
- Used when creating explorations. Draws from the single pool of exploration fields defined in Settings → Fields. The Steps field type is not available for exploration fields and therefore not available in exploration templates.
Both tabs list templates the same way and open the same full-page editor. A template has a name, an enabled state, its chosen fields and its project scope — it carries no icon and no colour.
What users see. When a user creates a test case or exploration, they see a Template control. In the new-case panel it starts empty, and a case saved without one lands on the workspace default template. Switching templates reloads the visible fields immediately. The template decides which fields appear — users cannot add or remove fields; that is admin-only configuration. Whether a field is required, and what value it starts from, is a per-project setting on the field itself — see Project Overrides.