Fields
Fields are reusable custom metadata inputs that admins define at the workspace level. They appear on test cases, test results, and test sessions — letting teams capture structured data that matters to the way they work.
Who can manage fields?
The Fields page is at Settings → Fields and is accessible to Tenant Admins and Project Admins.
| Action | Required Access |
|---|---|
| View the Fields page | Tenant Admin, Project Admin |
| Create a field | Tenant Admin, Project Admin |
| Edit a field | Tenant Admin, Project Admin |
| Delete a field | Tenant Admin, Project Admin |
| Configure project overrides | Tenant Admin, Project Admin |
Three contexts, one page
Settings → Fields is a single page with three tabs. The tab you are on is part of the address, so a link to a tab reopens on that tab, and leaving for the field editor and coming back lands you where you were.
| Tab | Where the field appears | Types |
|---|---|---|
| Test case fields | On a test case, when it is written or updated. | All 10, including Steps. |
| Test run fields | On the result form, when an execution is recorded. | 9 — Steps is not offered. |
| Exploration fields | On an exploration. | 9 — Steps is not offered. |
The three are separate families: a field defined on one tab is not available on another. If you need the same fact captured on both a case and an exploration, define it twice.
Field Types
All 10 field types — Long text, Dropdown, Steps and the rest — and which contexts each one is offered in.
Test Case Fields
The Test case fields and Test run fields tabs — the list, the editor, presentation, and deleting a field.
Exploration Fields
The Exploration fields tab — and how these differ from test case and test run fields.
Project Overrides
Override groups in the field editor — which projects, required state, and default values.