Manage Fields
The Manage Fields screen allows you to add or remove customizable fields across different assets. It includes two sections:
User Defined Fields (UDFs): Custom fields that you can add to different modules as needed.
System Defined Fields: Predefined fields that you can edit but cannot delete.
You can add UDFs of the following types:
String
Large Text
Lookup List
Multi-Select Lookup List
Cascading List
Number
Date Picker
Creating New Fields
To create new custom defined fields, perform the following steps:
 |
Go to Customization and select Manage Fields.
Click New.
Select the Field Type and enter requested details.
Field Name: A unique ID that remains same across projects.
Field Label: A field alias that you can change for each project.
Lookup List: Enabled only when the Field Type is Lookup List, Multi-Select Lookup List or Cascading List. Select from existing lists or click Add List to create a new one.
Field Length: Enabled only when selected field type is "String". Specify a maximum number of characters (limit is 255 characters).
Select the Projects to add a new custom field.
Select the Modules to associate with the new custom field.
Click Add Project.
Set a Default Value for the UDF to auto-populate the field when a new entity is created in the associated modules.
Click Save.
The system adds the UDFs to the Default Section of the respective module layout, if Layout Management is enabled on the QMetry instance.
Note
Field Name has limit of 50 characters and Field Label has limit of 100 characters.
Before adding a new UDF, review existing UDFs under the User-Defined Fields to avoid creating duplicates.
Cascading fields and their values in Test Assets remain specific to the project in which they are created. You cannot copy or move cascading fields and values to other projects.
Custom reports include only non-cascading fields.
The system does not support Cascading Lists for Automation API and Test Case created using BDD Import/Create features.
Editing Existing Fields
You can edit existing UDFs to change the field label, field length, and project mapping. The field type and field name remain non-editable.
To edit an existing UDF, perform the following steps:
Go to Manage Fields under Customization.
Click Edit under the Actions column.
Make necessary edits.
Note
System defined fields are non-editable.
Sharing Fields Across Projects or Modules
You can share UDFs across projects or modules from the Add or Edit screen in Manage Fields.
Notes
To use a UDF in a project, you must map the field to the projects.
You can map only those projects that you have access to.
To share fields across projects or modules:
Go to the Customization and select Manage Fields.
Click New to create a UDF or Edit to update an existing one.
Select the projects where you want to use the UDF and click Add Project.
Choose the modules to map the UDF. You can select multiple modules from the dropdown.
Enable the Mandatory toggle to make the UDF required.
In case of Lookup List, MultiLookup List, or Cascading List, the system maintains the list values individually for each project. You can edit the List or set default values for the list for each project.
 |
Marking Fields as Mandatory
Note
You need “View” and “Modify” permissions for Customization to set fields as mandatory.
Fields with grey background are not editable.
Admin can set important system and user defined fields as mandatory.
Go to Customization and select Manage Fields.
Expand the User Defined Fields or System Defined Fields.
Find the field to mark as mandatory and click Edit under the Actions column.
Turn the Mandatory toggle On to mark the field as required.
You can configure the mandatory setting separately for each module and project.
Show Testing Type Field
Use the toggle on the Manage Fields screen to show or hide the Testing Type field across the application. By default, the toggle is On, making the field visible in the Test Case grid and column list.
If the field is part of any saved filters, those filters will be cleared automatically when the toggle is changed. You can turn the toggle Off to hide the field from view.
 |
Note
This setting does not impact Dashboards or Reports.
The Testing Type field remains visible even when the Show Testing Type is turned off.
Defining Default Value for Particular Field
Set default values for fields to automatically populate the value when a new record is added in the relevant project or module. You can configure default values for both User Defined and System Defined Fields at the project level.
Note
You need Customization “View” and “Modify” permissions to add default values.
You can set default values for all fields except LARGETEXT or DATETIMEPICKER type, or for the Associated Release(s), Summary, and Testing Type fields.
To set a default value, perform the following steps:
Go to Customization and select Manage Fields.
Expand System Defined Fields.
Select the Field Label and click Edit under Actions.
For LookUp, Multi LookUp, or Cascading List fields, select a value from the list. List values are maintained per project, so the default value for a single list may vary across projects. For other field types, enter the value in the input box.
Copying List Values to Other Projects
You can copy the Field List Values from the current project to other projects. To do so, you must have the following permissions:
Source/Destination Project | Permissions |
|---|---|
Source Project | You must have Project and Customization “View” permissions. |
Destination Project | You must have the Project “View” permission, Customization “View” and “Modify” permissions. |
To copy list values from other projects:
Go to Customization and select Manage Fields.
Expand the System Defined Fields section.
Find the label to update and click Edit under Actions.
In the Project Mapping section, click Edit List.
Select the list values to copy. You can select a maximum of 100 list values at a time.
Click Copy and select the destination projects.
To monitor the copy progress, go to Scheduled Tasks under Notifications.
Importing List Values from Other Projects
Import field list values from other projects to reuse existing data.
To create or modify any list, you must have the following permissions:
Source/Destination Project | Permissions |
|---|---|
Source Project | “View” permission for Project and Customization |
Destination Project | “View” permission for Project and “View” and “Modify” permissions for Customization. |
To import list values from other projects
Go to Customization and select Manage Fields.
Expand the System Defined Fields section.
In the Actions column, click Edit for the field you want to import list values into.
Click Edit List for the project in the Project Mapping section.
Click Import.
Open the drop-down and select the project from where you want to import the list values.
Select the values to import and click Import. You can select a maximum of 100 list values at a time.
Deleting Fields
You can delete only user-defined fields. You cannot delete system-defined fields.
Before you delete a field, remove it from all linked projects.
Note
When you delete a UDF, the system permanently removes its data.
Before you delete a field, make sure no test assets in any module use it.
Removing Association of Fields
To remove an association of fields from the project, perform the following steps:
Set the current project to the QMetry project you want to remove the UDF association.
Go to the Customization and select Manage Fields.
Find the UDF in the list and click the Edit button for that field.
In the Project Mapping section, click the Delete icon under the Action column to remove the field’s association with the current project.
Note
Once you unassociate the field, the system deletes all its values from test assets in that project, and you cannot recover them.
If the field has assigned values, the system shows a confirmation message. Remove it from all projects first.
If you delete a UDF of type Lookup List or Multi Select Lookup List from a project, all values assigned to related entities change to “None".
You can change these settings only if the Customization package is enabled on your QMetry instance.