Field Settings

Use Field Settings to control which fields appear on each object in an individual project. You can rename system fields, add project-specific custom fields, hide optional fields, and change the field display order.

Before you start

You need Project Admin permissions to manage project settings.

Access your field settings

You can find Field Settings in Project settings.

From here, select objects in the Artifacts panel on the left to edit or add fields to that object.

Understand field types

You can choose from the following objects: Release, Build, Requirement, Test Case, Test Suite, Test Run, or Defect.

These objects can have the following field types:

  • System field: Any field created by qTest Manager.

  • Custom field: Any field created by a qTest user, either at the project level or the site level.

  • Inherited field: Any field that inherited content from another object. For example, a test run can inherit fields from a test suite, such as Execution Type or Environment.

  • Site field: A system field or a custom field that is managed at the site field level. A field managed at the site field level can exist across multiple projects.

Modify a system field

System fields are the generic fields qTest has on an object. Use these fields to capture basic information.

Deactivate system fields

You can't delete system fields, but you can deactivate some of them to hide them from the object. Clear the checkbox in the Active column to deactivate the field on all objects of that type.

Not all system fields can be deactivated. If the checkbox next to the system field is grayed-out, it can't be deactivated. For example, a Build object has Status, Build Date, and Build Note system fields. You can deactivate the Build Note field, so it won't display on build objects. However, you can't deactivate Status or Build Date.

Reorder system fields

To change the order of fields on an object, select the up or down arrow next to a field in the Action column.

You can also select Preview to review the field layout on the object before you save your changes.

Edit system fields

You can edit parts of system fields to fit your needs. To edit a system field, select the field you want to edit in the Display name column.

What's editable depends on the system field you're working with. Here are the ways you can edit system fields:

  • Display name: You can edit the display name of any system field. Display names can have a maximum of 100 characters.

  • Required: If a system field isn't required, but you want it to be, select the Required checkbox. If a system field is required by default, you can't change it to optional.

  • Default Value: You can add or select a default value for most Rich text editor, Combo box, Text area and Text box system fields. You can also add default values for some Date picker or Date and time picker system fields, such as the defect Target Date field.

  • Combo box values: You can edit most combo box values. Depending on the respective system field combo box, you may be able to add new values, change value names, deactivate or delete values, choose a custom color for a value, or change value order. Note that you can't edit the combo box options for Release or Build statuses.

Add custom fields

Create custom fields when your project needs information that system fields don't cover.

To add a custom field, follow these steps:

  1. From the Artifacts menu, select the object you want to add the custom fields to: Release, Build, Requirement, Test Case, Test Run, Defect.
  2. Select Add Custom Field and define the field's Display Name.

  3. Choose the Field Type you want to create from the dropdown, then select OK. You can now create any of the following field types:

    • Text box: A single-line field for short text.

    • Text area: A field for longer text.

    • Combo box: A dropdown with multiple values where you can select one option.

    • Multiple selection combo box: A dropdown with multiple values that lets you select more than one option.

    • Date picker: A small on-screen tool that lets you select a date.

    • Date and time picker: A small on-screen tool that lets you select a date and time.

    • User list: A roster that lets you pick from a list of users available in qTest.

    • Rich text editor: A text field that can include basic formatting, such as bold, links, and lists.

    • Number: A field that only accepts numeric values.

    • Check box: A control that displays multiple selectable options to choose one or more of.

    • URL: A field where you can enter a link.

  1. Edit your custom field as applicable. You can choose the following options:

    • Description: Enter a description of this field's purpose and an example value for this field. AI Chat uses this field when it creates content for your custom fields.

    • Required: Select the checkbox to make the field mandatory. This means users have to fill out the field before they can save the object.

    • Searchable: Select the checkbox to make the field searchable. Note that you can't make the User list, Date picker, or Date and time picker fields searchable.

    • Default Value: Specify a default value that qTest will displays if users don't edit the field. For fields that allow multiple selections, you can define more than one default value. For fields that include the date and/or time, you have the option to make the current date and time the default value. The User list is populated with active project users, and you can't select a default value for this field.

    • Value: If your custom field has multiple options, you'll define multiple values for your users to choose from. For Combo box, Multiple selection combo box, and Check box fields, select Add Value to create a new value, then select the Active checkbox next to that value.

Inherited fields

Inherited fields have values passed from a parent object in your test organization. You can't edit the properties of any inherited fields, only the source fields. For example, if you want a different value for a custom field of a test run, you need to edit the custom field on the parent test suite. You can re-order inherited fields.

Certain system fields are inherited. This means that the value you add to the first system field updates the value for objects that contain the inherited field. For example, the Environment system field on a test suite becomes an inherited field on test runs and defects. Then, a defect inherits the Environment field from the test run. When you edit the Environment field for a test suite, it updates the inherited Environment fields for associated test runs and defects.

Custom fields created on test suites are automatically inherited in test runs. The total number of custom fields on a test run includes inherited custom fields from the test suite.

What's next

Set up site fields to reuse fields across projects and include them in Insights reports.