Field Settings

Each project in qTest Manager has its own set of fields and field settings.  You must have Project Administration permissions to use the field settings functionality.  To manage the fields for a given project, perform the following steps.  

  1. Select the project.
  2. Click the Gear icon.  Then, select the Field Settings option from the drop-down list.  The Release page is displayed.                                                                                                                                                                  
  3. There are 3 different categories of fields.
  • A system field is a default field created by qTest Manager.  
  • A custom field is a field created by the user for a given project.   
  • An inherited field is a field passed down from another artifact.

In the screenshot shown below, the five fields for the Release object are system fields. 

In the following example, when we select the Test Run artifact from the left panel, the Environment field is inherited.   

The environment is passed down from the Test Suite to the Test Run.  Therefore, when you add a test run to a test suite, the test run will inherit the Environment value from the test suite. "Environment" is a special system field that will be automatically updated in test runs and defects as an inherited field when you add/edit its values in the test suite.

The field settings functionality can be used to modify existing system fields, create custom fields, and reorder the field display order.  

Modifying System Field

System fields are provided by default to help users define basic information for creating qTest Manager objects.  Accordingly, users cannot delete System Fields but all display names of system fields are editable.  qTest Manager allows a maximum of 100 characters

To modify an existing system field, perform the following steps:

  1. Select the applicable artifact in the left panel.  Each artifact (e.g., Release, Test Case, Test Run, etc.) has its own set of fields.  In this example, we will select the Test Run artifact from the left panel.  

  2. Select the system field you want to modify by clicking on the field in the Display Name column.  In the following example, we will click on the Status field.  The Edit System Field screen displays with information specific to the selected field.

    INT: The following types of changes can be made to a system field.  1.) You can change the field’s Display Name.  2.) You can add values to be associated with the field or change existing values for pick list field types.   

  3. In the Display Name field, change the field’s display name to Execution Status.
  4. Click the Add Value button.  Enter the New Value name in the Display Name column.

    he status field of the test run is unique as it also allows you to click the Color field for the new value.

    INT:  You can also change the color associated with an existing value by clicking the Color field for the value and selecting a different color.  If you want to hide a value for this field, you can make the value inactive by de-selecting the check box in the Active field for that value.
  5. Click the OK button to save your changes.    


  • Rich Text Editor, Text area, or Text box: Display Name and define Default Value are editable.
  • Combo box: Display Name and Values are editable. 
    • You can customize all Status fields of Requirements, Test Cases, Test Runs, and Defects.
      • You can map colors to Statuses of Test Runs and Defects in their Field Settings.
    • Some combo-box System Fields will automatically populate values and you can ONLY set their Default Values, including Affected Release/BuildFixed Release/Build, Module, and Target Release/Build in Defects.
    • For Target Release/Build in Test Suite, you can only change Display Name.
  • User-list, Auto-filled, and Date Picker: Only the Display Name is editable.  For the field "Target Date" of Defect, you can set Current Date or a Default Value for Target Date.

Hiding Fields from the Display

Some fields, such as the Configuration field, can be hidden from the display.  Some fields, such as the Status field, are required fields and cannot be hidden.  To hide a field for a given artifact, you can make the field inactive by de-selecting the check box in the Active field for that field.  

Reordering a Field Display

To reorder the field display, perform the following steps. 

  1. Select the applicable artifact in the left panel.  In this example, the Test Suite artifact has been selected.

  2. Similarly, you can also drag and drop the field rows into the preferred order.
  3. Click the Preview button to review your work.  The Preview Test Suite fields page is displayed.  The Status field is now displayed in the top right of the page.  
  4. Click the Back button.  The Test Run page is redisplayed.  Click the Save button to save your changes. 

Adding Custom Fields

  1. Select an artifact from the left panel.  In this example, we will select the Defect artifact.  The Defect page is displayed.

  2. Click the Add Custom Field button.  The Add Custom Field screen is displayed. In the Display name field, enter the field name.  Click the down arrow to the right of the Field type field and select the type of field from the drop-down list.  In this example below, the Combo box field type has been selected.

  3. Click the OK button.  The Edit Custom Field screen is displayed.

  4. Select the Required check box to make the field required.  In this example, a tester must fill in this custom field to save the defect.  

  5. For certain field types, such as Combo box, Multi selection combo box, and Checklist, you can define the values for the field.  To do so, click the Add Value button.  In the Display Name field, add a value associated with this field.  Repeat this step as needed to add all the values associated with the field.

    Optionally, select the Default Value radio button to set a default value.  In the example shown in the following screenshot, when a tester creates a new defect, this required field will auto-populate with ‘Microwave’ as the value.  


  6. Click the OK button to save your changes and redisplay the Defect page.  The following example shows a new custom field called Ready For Retesting that has a field type of ‘checkbox’ and ‘Yes’ and ‘No’ values.   

Description of each field type:

Field Type Description  
Rich text editor     Multiple lines text input area integrated with an editing toolbar, maximum input characters allowed
Text box Single line text input area without editing toolbar, maximum input characters allowed = 300.  
Text area Multiple lines text input area without editing toolbar, maximum input characters allowed = 500
Combo box Drop-down lists combined with a single-line editable textbox, allowing users to enter text to search.
User list   Control that get all active users directly from database and display on screen for selection. Only one user can be selected at a time.
Auto-filled Label-style fields that automatically display some information such as user names, date and time, etc…
Date picker Control that allow users to select a specific date

Editing Inherited Custom Fields

All Custom Fields you create in the test suite will be automatically added in the Test Run's Field Settings as Inherited Fields.  The total number of Custom Fields in Test Run must include Inherited Custom Fields from the test suite and custom fields of the test run itself.


  • You can only reorder Inherited Custom Fields' display in Test Run's Field Settings using Move Up and Down arrows.
  • You cannot edit Inherited Custom Fields in Test Runs, but you have to edit the Source Fields in the test suite's field settings.  Then, they will be automatically updated in Test Run's Fields
  • To remove Inherited Custom Fields of Test Runs, you have to delete the Source Fields in Test Suite.
  • Currently, there is no option to hide Inherited Custom Fields from Test Suite in Test Run


Subscribe To Our Blog
Powered by Zendesk