Field Configuration
Toggle field visibility and set mandatory flags for built-in fields in your project.
Overview
Field Configuration lets you control which built-in fields are visible on test case forms and whether they are required. Unlike custom fields (which add new user-defined fields) and field defaults (which set default values and options), Field Configuration focuses on visibility and mandatory settings for the standard fields that ship with every project.
This is useful when your team does not use certain built-in fields and wants to simplify the test case creation form by hiding them.
Toggle Field Visibility
You can show or hide built-in fields on test case forms:
- Navigate to Settings → Field Configuration within your project.
- You will see a list of all built-in fields with toggle switches.
- Toggle a field off to hide it from the test case creation and editing forms.
- Toggle a field on to show it again.
When a field is hidden:
- It does not appear on the Create Test Case or Edit Test Case forms.
- Existing values for that field are preserved — hiding a field does not delete any data.
- The field can be shown again at any time, restoring it to forms with all data intact.
Hiding unused fields simplifies the test case form for your team. If your project does not use the Environment or Automation Status fields, hide them to reduce visual clutter.
Set Mandatory Flags
For visible fields, you can control whether they are required when creating or editing test cases:
- Navigate to Settings → Field Configuration.
- Find the field and toggle the Required switch.
- When required, users must provide a value for this field before saving a test case.
Some core fields (like Title) are always required and cannot be made optional. The Required toggle only appears for fields where it is applicable.
Per-Project Configuration
Field Configuration is scoped to each individual project. You can have different fields visible and different mandatory settings across different projects. This allows teams to tailor the test case form to their specific workflow without affecting other projects.
Special Fields
automation_ids
The Automation IDs field is a virtual/computed system field. It surfaces the Automation IDs linked to a test case and powers the Automation Runs UI.
- Default visibility: On
- Mandatory: Not applicable (computed field — cannot be required)
- Scope: Per project, like all other field configuration settings
When visible, automation_ids appears in:
- The Automation IDs section on the test case detail page
- The test case drawer in test cycles
- The Automation Runs card on the execute page
- Table columns on the test cases and test cycle test cases tabs
- Filter modals (filter by automation ID)
When hidden (toggled off), all of the above UI is cleared — but API ingestion still works. The reporter can continue to resolve automation IDs and store execution results. This is deliberate: toggling the field off should never break an existing CI/CD pipeline. It simply hides the feature from the UI for teams that do not use automation, or who prefer a simpler test case form.
Difference from Custom Fields
It is helpful to understand the distinction between these related settings:
| Setting | What It Controls |
|---|---|
| Custom Fields | Adds new user-defined fields (text, dropdown, date, number) to test cases. Up to 10 per project. |
| Field Defaults | Sets default values and manages available options for built-in fields (priority, status, severity, etc.). |
| Field Configuration | Toggles visibility (show/hide) and mandatory flags for built-in fields on the test case form. |
These three settings work together to give you full control over which data fields appear on your test case forms, what their default values are, and which are required.
Related Documentation
- Custom Fields — Add user-defined fields to test cases.
- Field Defaults — Configure default values and options for built-in fields.