Field Defaults
Set default values for status, priority, severity, and other built-in fields in your project.
Overview
Field Defaults let you configure the default values and available options for built-in test case fields within a project. While custom fields let you add entirely new fields, Field Defaults focuses on the standard fields that come with every project — like Status, Priority, and Severity.
By configuring field defaults, you ensure that new test cases start with sensible values and that dropdown options match your team's terminology and workflow.
Default Values
You can set default values for built-in fields so that new test cases are pre-populated with your preferred starting values. This saves time and ensures consistency when team members create test cases.
Configuring Default Values
- Navigate to Settings → Field Defaults within your project.
- Find the field you want to configure (e.g., Priority, Status, Severity).
- Select a default value from the available options.
- Click Save. New test cases will use this default going forward.
Changing a default value only affects new test cases created after the change. Existing test cases retain their current values.
Tag-Based Options Management
For fields that use a predefined set of options (like Priority, Status, and Severity), you can manage the available options using a tag-based interface.
Adding Options
- Navigate to Settings → Field Defaults.
- Find the field you want to update.
- Type a new option value in the input field.
- Click Add or press Enter to add the option.
- The new option is immediately available in the dropdown on test case forms.
Removing Options
- Find the option you want to remove.
- Click the X icon next to the option tag.
- The option is removed from the dropdown. Existing test cases with this value retain it, but it will no longer be available for new selections.
Some fields have required options that cannot be removed. These are core values necessary for the system to function correctly (e.g., certain status values that the execution engine depends on).
Mandatory Fields
You can mark built-in fields as mandatory or optional for your project:
- Mandatory fields must be filled in before a test case can be saved.
- Optional fields can be left blank.
To toggle a field's mandatory status:
- Navigate to Settings → Field Defaults.
- Find the field and toggle the Required switch.
- When enabled, the field becomes mandatory on all test case forms in the project.
Only make fields mandatory if they are genuinely required by your workflow. Too many mandatory fields can slow down test case creation and frustrate your team.
Scope
Field defaults are configured per project. Each project has its own independent set of default values and options. Changes in one project do not affect other projects in your organization.
This allows different teams to use different terminology or priorities. For example, a mobile testing project might have different severity options than a backend API project.
Related Documentation
- Custom Fields — Add entirely new fields beyond the built-in set.
- Field Configuration — Toggle field visibility and mandatory flags for built-in fields.