Using Custom Fields
Custom fields in QAM Hub let you capture structured data on your test cases beyond the built-in fields — for example priority, test type, component, or automation status. Instead of burying this information in the description, custom fields make it consistent, filterable, and reportable across your project.
This guide covers the field types available, how to create and order them, and how to fill them in on test cases. To set up the test cases themselves first, see creating test suites and test cases.
What custom fields are for
Custom fields turn ad-hoc notes into structured attributes. Common uses include marking a test's priority, classifying its type (functional, regression, smoke), tagging the component it covers, or recording whether it is automated. Because the data is structured, you can use it consistently across every case rather than relying on free text.
Available field types
QAM Hub supports several custom field types, so you can match the field to the kind of data it holds:
- Text — a short single-line value.
- Textarea — a longer multi-line value.
- Checkbox — a yes/no or true/false value.
- Dropdown — a single choice from a predefined list of options.
- Number — a numeric value.
Creating a custom field
- Open your project's settings, where custom fields are managed (this requires a project or organization admin role — see roles and permissions).
- Create a new custom field, give it a clear name, and choose its type from the list above.
- For a dropdown, define the list of options testers can choose from.
- Set the field's order so it appears in a logical position on the test case form.
Filling in custom fields on a test case
Once a field exists, it appears on every test case in the project, where testers fill in its value alongside steps and expected results. Because the values are structured, they stay consistent across the whole suite and can be used to organize and report on your tests.
Custom fields and templates
Custom fields work hand in hand with test case templates: a template can include its own template-specific custom fields, so cases created from it start with exactly the right structure. This is the fastest way to keep a large test base consistent.