Using & Managing Fields

Use custom fields in forms, filters, and CSV operations, and manage field lifecycle.

Using Custom Fields

Once custom fields are created, they become part of the daily workflow for everyone on your team. Here is how custom fields integrate into different areas of TestKase.

Custom fields appear on both the Create Test Case and Edit Test Case forms. They are displayed below the built-in fields in the order they were created. Each field renders with the input control for its type:

TEXT fields render as a free-text input.
NUMBER fields render as a numeric input.
CALENDAR fields render as a date picker.
SINGLE_LIST fields render as a dropdown where users pick one option.
MULTI_LIST fields render as a multi-select dropdown where users can check multiple options.

Custom fields are optional by default, so testers can leave them blank. If a field has been marked Mandatory on Field Configuration, the create and edit forms will not save until it has a value.

Test Case Detail View

Custom field values are displayed on the test case detail page alongside the built-in fields. They appear in a dedicated "Custom Fields" section, making it easy to see all the metadata associated with a test case at a glance.

Filtering by Custom Fields

Custom fields can be used to filter test cases in the test cases list view. When you click the Filter button, custom fields appear as additional filter options below the built-in filters.

SINGLE_LIST — Select one or more options to filter by.
MULTI_LIST — Select one or more options; test cases matching any selected option are shown.

Combine custom field filters with built-in filters for powerful queries. For example, filter by Priority = Critical AND Browser = Safari to find all critical test cases targeting Safari.

CSV Export with Custom Fields

When you export test cases to CSV, all custom fields are included as additional columns in the exported file. The column headers use the custom field names, and the cell values contain the field values for each test case.

A custom field is only exported if its column is currently visible in the test case table — the export writes exactly the visible columns. Use the column configuration control before exporting if you need a custom field included.

For list-type fields, exported values work as follows:

SINGLE_LIST — The selected option label is exported as a plain string.
MULTI_LIST — Multiple selected options are exported as a comma-separated string in a quoted cell (e.g., "API, Auth, UI").

CSV Import with Custom Fields

When importing test cases from a CSV file, you can include custom field values by adding columns with headers that match your custom field names exactly (case-sensitive). The importer will map the CSV columns to the corresponding custom fields.

Title,Priority,Status,Browser,Affected Modules,Story Points,Release Date
"Login with valid credentials",Critical,Approved,Chrome,"Auth, API",5,2026-03-15
"Search product by name",Minor,Approved,Firefox,UI,3,2026-03-20
"Checkout with discount code",Blocker,Approved,Safari,"API, UI, Database",8,2026-04-01

For MULTI_LIST fields in CSV imports, separate multiple values with a comma and quote the whole cell — for example "Auth, API". The importer splits these cells on the comma; a pipe character is not a separator and Auth|API is read as one literal value.

For CALENDAR fields, use the YYYY-MM-DD date format. A value that does not match one of the field's configured options is reported as a row error on the Preview & Validate screen, listing the allowed values, and that row is skipped — it is not silently ignored.

Managing Fields

As your project evolves, you may need to change or remove custom fields. The Custom Fields settings page itself supports creating and deleting fields only, but two other settings pages configure an existing field without recreating it:

Field Value — add or remove the options a list field offers.
Field Configuration — turn the field's Mandatory and Visibility toggles on or off.

A field's name and type cannot be changed after creation, and fields cannot be reordered. To change either, delete the field and create a new one.

Deleting a Custom Field

To delete a custom field entirely, click the Delete icon on the field row in the Custom Fields settings page. A confirmation dialog will appear because this action has significant consequences:

The field is permanently removed from the project.
All values for this field across every test case in the project are no longer associated with a field.
The field is removed from test case forms, the detail view, and filters.
Future CSV exports will no longer include the deleted field as a column.
This action cannot be undone.

Deleting a custom field permanently removes it from the project. This action cannot be undone. Deleting and recreating is the only way to change a field's name or type.

What Happens to Change History

When a custom field is deleted, the change history entries that reference that field remain in the test case change history. Historical records show the field name and the old/new values, providing an audit trail even after the field no longer exists.