Field Value
Manage the allowed options for list-type test case fields in your project.
Overview
The Field Value page controls the set of allowed options for the list-type fields on a test case
within a project. It is where you decide, for example, that Priority offers Blocker, Critical,
Major, Minor and Trivial, or that Environment offers QA and DEV.
Only fields that store a list of options appear here. The built-in list fields are Priority,
Status, Automated, Environment, Features, Platform and Labels, plus any
SINGLE_LIST or MULTI_LIST custom field in
the project. Free-text, number and date fields have no option list and are not shown on this page.
TestKase does not support per-field default values. There is no control on this page — or anywhere else — that pre-fills a field on a new test case. New test cases start empty for every optional field.
Managing options
- Navigate to Settings → Field Value within your project.
- Each field is shown as a box containing its current options as tags.
- Type a value into a field's box and press Enter to add it. You can add several values at once by separating them with commas before pressing Enter.
- Click the × on a tag to remove that option.
- Click Submit to save. Nothing is applied until you submit — Cancel reloads the page and discards every unsaved change.
Fields you have edited are highlighted until you submit, and leaving the page with unsaved changes prompts you to confirm.
Rules enforced when you add or save options
- An option can be at most 25 characters. Longer values are rejected by the input and are dropped silently if they reach the API.
- Duplicate options are removed, ignoring case —
Chromeandchromeare the same option. - A field marked Mandatory on Field Configuration must keep at least one option; removing the last one is blocked.
- Status must always keep the value Archive. The Archive view in the test case sidebar depends on it, so that tag cannot be removed.
If some of the fields you submitted fail these checks, the valid ones are still saved and the page reports which fields were rejected and why.
Removing an option
Removing an option only affects new selections. Existing test cases that already hold that value keep it, but the value is no longer offered on test case forms or in filters.
Mandatory fields
Whether a field is required is not set on this page. Mandatory and visibility toggles live on the Field Configuration page. Field Value only decides which options a field offers.
Scope
Field values are configured per project. Each project keeps its own independent option lists, so a mobile project and a backend API project can offer completely different environments or platforms without affecting each other.
Related Documentation
- Custom Fields — Add entirely new fields beyond the built-in set.
- Field Configuration — Toggle field visibility and mandatory flags.