⚠️Custom Fields are available in Startup, Business, and Enterprise subscriptions
Every test case, test run, and defect in Qase comes with a standard set of properties.
Custom fields let you add your own. Need to track a regulatory requirement ID on every test case? A deployment target on each run? A severity sub-category on defects? Create a custom field once at the workspace level and apply it wherever it belongs.
Each custom field is scoped to a single entity type (test cases, test runs, or defects). If you need to capture similar data across entity types, create a separate field for each.
Fields can be enabled for all projects at once or limited to specific ones, no need to duplicate a field just because multiple projects need it.
Creating a custom field
Navigate to Workspace → Fields and select + Create New Custom Field. Configure the following:
Title (required) — a descriptive name that will appear on every entity form.
Entity — choose one: Test Cases, Test Runs, or Defects. This cannot be changed later.
Type — the data type for the field. Choose from:
Type | Use case |
Text | Free-form short text |
Text area | Multi-line text (notes, descriptions) |
Number | Numeric values |
Checkbox | Boolean on/off |
URL | Validated link |
Selectbox | Single choice from a defined list |
Multiselect | Multiple choices from a defined list |
Important: A field's type is permanent. Once created, you cannot convert a selectbox into a multiselect or change a number field to text. Plan your field type carefully.
Enable for all projects — toggle on to make the field appear everywhere, or select specific projects.
Placeholder — sample text shown in the empty field to guide users.
Default value — auto-populated value that prevents blank submissions.
Required — when checked, the parent entity cannot be saved until this field has a value.
Configuring selectbox and multiselect values
For selectbox and multiselect types, define the list of allowed values:
Add values using the + button.
Drag values by the grip handle to reorder them.
Optionally customize each value's icon color (hex codes supported) and icon glyph (Font Awesome
fas fa-prefix).Remove a value with the delete button.
Ordering fields
By default, custom fields appear in chronological order, newest at the bottom. To change this, open any field in Workspace → Fields and set its order value. Lower numbers appear first. If two fields share the same order value, creation time breaks the tie.
Sort the field list by the order column to confirm your arrangement.
Using custom fields
Once created, custom fields appear automatically on the relevant entity forms. When creating or editing a test case (or run, or defect), fill in the custom field values alongside the standard properties. Required fields block saving until completed.
Custom fields are also available in QQL queries, you can filter, group, and report on custom field values just like built-in properties.
Export behavior
When you export test cases to CSV, custom fields appear as additional columns on the far right of the file. Column headers follow the pattern cf_1, cf_2, cf_3, matching the creation order of your fields in workspace settings, not the display order you may have configured.
FAQ
Can I change a custom field's entity type after creation?
No. Entity type and field type are both locked once the field is saved. If you need the same data on a different entity, create a new field.
What happens to data if I remove a project from a field's scope?
The field and its values are hidden in that project but not deleted. Re-enabling the project restores the data.
Can I use custom fields in automations or API calls?
Yes. Custom fields are exposed through the Qase API and can be set programmatically when creating or updating entities.