Overview
Qase ships with a set of system fields (Priority, Severity, Status, etc.) that appear on every test case by default.
The Fields page in Workspace Management lets you toggle these on or off, customize their values, and — on qualifying paid plans — create custom fields to capture any additional data your team needs.
You can access field settings from Workspace → Fields or by selecting Configure fields while editing a test case.
System fields
System fields are built-in and available on every plan. Each can be switched off if your team doesn't use it — disabled fields won't appear in test case forms.
Field | Purpose |
Priority | Case priority: Not Set, Low, Medium, High |
Severity | Case severity: Trivial, Minor, Normal, Major, Critical, Blocker |
Type | Testing type: Functional, Smoke, Regression, Security, Usability, etc. |
Behavior | Positive, Negative, Destructive, or Not Set |
Status | Active, Draft, or Deprecated |
Layer | End-to-end, API, or Unit |
Is Flaky | Flag unstable test cases |
Automation Status | Automated or Manual |
To be automated | Checkbox for manual cases planned for automation |
Description, Pre/Post Conditions | Free-text context for the test case |
Customizing system field values
On paid plans, you can modify the value options for system fields. For example, you might add a “P0” priority level or rename severity labels to match your team's terminology.
Navigate to the field in Workspace → Fields, select Edit, and modify the values list.
Result status customization
The Result Status system field controls the possible outcomes when executing a test case in a run (Passed, Failed, Blocked, Skipped, etc.).
You can add custom result statuses to match your workflow — for example, “Skipped – Environment Issue” or “Passed with comments”.
Custom fields
Custom fields let you attach structured metadata beyond what system fields cover. Use them for anything specific to your process: Sprint, Component, Risk Level, Regulatory Requirement, or any other property.
Custom fields can be applied to:
Test cases — appear in the case editor and detail view
Test runs — appear as run-level properties
Defects — appear in the defect form
To create a custom field, go to Workspace → Fields → Custom Fields and select Create.
Choose a field type (text, number, dropdown, multi-select, checkbox, etc.), set the field name, and optionally restrict it to specific projects.
FAQ
Can I disable a system field for one project but keep it for others? Yes. System field visibility can be toggled for specific projects.
What happens to existing data if I disable a system field? The data is preserved — it just isn't displayed. Re-enable the field and the values reappear.
Can I make a custom field required? Yes. When creating or editing a custom field, enable the “Required” option. Users won't be able to save a test case (or run, or defect) without filling it in.