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

The custom-field limit on Free

Free includes 5 custom fields, counted across test case, run-result and exploration fields together; built-in fields such as Steps don’t count. Starter and above are unlimited. At the limit only New field is blocked: it stays in place, disabled, under a one-line note — “All 5 custom fields on Free are in use — delete one you no longer need, or move to Starter for unlimited fields.” — with Upgrade to Starter for a billing admin or Ask for anyone else. Every existing field keeps working and stays editable, including after a downgrade. See Plans and Billing.

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.