Field Configuration

Overview

Field Configuration lets you control which test case fields are visible on forms and whether they are required. Unlike custom fields (which add new user-defined fields) and the Field Value page (which manages the options a list field offers), Field Configuration focuses on visibility and mandatory settings.

The page lists the built-in fields and every custom field in the project, each with a Mandatory and a Visibility toggle. The Test Case Versioning switch for the project also lives at the top of this page, under Project Features.

This is useful when your team does not use certain fields and wants to simplify the test case creation form by hiding them.

Toggle Field Visibility

You can show or hide fields on test case forms:

1. Navigate to Settings → Field Configuration within your project.
2. You will see a row per field with a Mandatory toggle and a Visibility toggle.
3. Turn Visibility off to hide the field from the test case creation and editing forms.
4. Turn it back on to show the field 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.

Set Mandatory Flags

You can control whether a field is required when creating or editing test cases:

1. Navigate to Settings → Field Configuration.
2. Find the field and turn its Mandatory toggle on.
3. Users must then provide a value for this field before a test case can be saved.

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
• Default mandatory: Off (the Mandatory toggle is available, like any other field)
• 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:

These three settings work together to give you full control over which data fields appear on your test case forms, which options they offer, and which are required.

Related Documentation

• Custom Fields — Add user-defined fields to test cases.
• Field Value — Configure the allowed options for list fields.