This document provides an explanation of the dropdown fields for all modules in QMetryQMetry has look up list and multi-lookup list fields across all the modules. Majority of the fields like Status, Priority, Test Category, Labels, etc. can be modified to have list values of your choice.
Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
→ The Default Value column contains either "Not Applicable" or "None."Default Values
No list values are set as default for any fields except for the “Testing Type“ test case field.
The default values listed against the fields are explained below:
Not Applicable: A default value cannot be assigned to the field.
None (System Default): The field has no default value assigned to it, but users can set the default value of their preference.
...
It is possible to set default values from Customization > Manage Fields > edit > set default value for each associated project for fields having their default values set to None.
Requirements Module Dropdown Fields
Field Label | Field Description | Field Type | Default Value | List Values |
Associated Release(s)/Cycle(s) | The Release and Cycle associated to |
the |
Requirement. The |
Releases and Cycles are |
added from Projects > Projects / Release / Cycle > Release / Cycle. | MULTILOOKUPLIST | Not Applicable |
User-entered values
Associated Release(s)
The Release to which the issue is associated. Releases are added from Projects > Projects / Release / Cycle > Release / Cycle.
LOOKUPLIST
Not Applicable
User-entered values
Project’s Release and Cycle associated with the Requirement. | |
Label(s) | Label(s) to categorize the |
requirements for the ease of |
search and use. | MULTILOOKUPLIST | None | Labels added under Projects > Labels section for the current project. |
MULTILOOKUPLIST
None
User-entered values
Issue Owner
Priority | Assigning a priority value to requirement. | LOOKUPLIST | None |
User-entered values
Issue Priority
Trivial, Blocker, Critical, Major, Minor OR any custom values added to the “priority“ list within the current project. | |||
Requirement Owner | Owner (assignee) of the Requirement. | LOOKUPLIST | None |
Trivial, Blocker, Critical, Major, Minor
Issue Status
Assigned user with access to the current project. | ||||
Status | To track the current status of the requirement. | LOOKUPLIST | None | Closed, Review Pending, In Progress, Requires Rework, |
Issue Type
The type of the issue that indicates whether it is a defect or a new funcationality/improvement.
LOOKUPLIST
None
Bug, New Feature, Enhancement
...
OR any custom values added to the “status“ list within the current project. |
Test Cases Module Dropdown Fields
Field Label | Field Description | Field Type | Default Value | List Values |
Associated Release(s)/Cycle(s) | The Release and Cycle |
associated to |
the |
Test Case. The Releases and Cycles |
are added from Projects > Projects / Release / Cycle > Release / Cycle. | MULTILOOKUPLIST | Not Applicable |
Project’s Release and Cycle associated with the Test Case. | |
Label(s) | Label(s) to categorize the |
test cases for the ease of |
search and use. | MULTILOOKUPLIST | None | Labels added under Projects > Labels |
MULTILOOKUPLIST
None
User-entered values
Priority
section for the current project. | ||||
Priority | Assigning a priority value to test case. | LOOKUPLIST | None | Trivial, Blocker, Critical, Major, Minor |
Requirement Owner
OR any custom values added to the “priority“ list within the current project. | |||
Test Case Owner | Owner (assignee) of the Test Case. | LOOKUPLIST | None |
Assigned user with access to the current project. |
Status |
To track the current status of the |
test case. | LOOKUPLIST | None | Closed, Review Pending, In Progress, Requires Rework, | |
Test Category | The Test Category to group the test cases of like attributes. | LOOKUPLIST | None | Security, Performance, Functional, Regression, UI, BVT OR any custom values added to the “Test Category“ list within the current project. |
Testing Type | This is a system field that cannot be selected from the QMetry UI or modified to have other list values. This field value is auto-updated by QMetry depending on the method of creating the test case. | LOOKUPLIST | Not Applicable | Manual, Automated - selected by system. |
...
|
Test Suites Module Dropdown Fields
Field Label | Field Description | Field Type | Default Value | List Values |
Associated Release(s)/Cycle(s) | The Release and Cycle |
associated to |
the Test Suite. The Releases and Cycles |
are added from Projects > Projects / Release / Cycle > Release / Cycle. | MULTILOOKUPLIST | Not Applicable |
User-entered values
Label(s)
Label(s) to categorize the requirement and for the ease of searching. Labels are added from Projects > Labels.
MULTILOOKUPLIST
None
User-entered values
Priority
Project’s Release and Cycle associated with the Test Suite. | |||
Test Suite Owner | Owner (assignee) of the Test Suite. | LOOKUPLIST | None |
Trivial, Blocker, Critical, Major, Minor
Test Case Owner
The user who has access over the project and who is going to work on the test case. Users are added from Customization > Users.
LOOKUPLIST
None
User-entered values
Status
Assigned user with access to the current project. | |||
Test Suite Status | To track the current status of the test suite. | LOOKUPLIST | None |
Approved, Review Pending, In Progress, |
Open
Rejected, On Hold, |
Open, New |
Test Category
The Test Category to group the test cases of like attributes.
LOOKUPLIST
None
Security, Performance, Functional, Regression, UI, BVT
Testing Type
The Testing Type values are assigned automatically to each test case as per the type of test case. The assigned Testing Type value it is not editable.
LOOKUPLIST
Not Applicable
Manual, Automated
...
OR any custom values added to the “Test Suite Status” list within the current project. |
Issues Module Dropdown Fields
Field Label | Field Description | Field Type | Default Value | List Values |
Associated |
Cycle(s) | The Cycle associated to the Issue. The Releases and Cycles are added from Projects > Projects / Release / Cycle > Release / Cycle. | MULTILOOKUPLIST | Not Applicable | Project’s Cycle associated with the Issue. |
Associated Release(s) | The |
Release associated to |
the |
Issue. The Releases and Cycles |
are added from Projects > Projects / Release / Cycle > Release / Cycle. |
LOOKUPLIST | Not Applicable |
User-entered values
Test Suite Owner
The user who has access over the project and who is going to work on the test suite. Users are added from Customization > Users.
LOOKUPLIST
None
User-entered values
Test Suite State
Project’s Release associated with the issue. | ||||
Label(s) | Label(s) to categorize the issue and for the ease of searching. Labels are added from Projects > Labels. | MULTILOOKUPLIST | None | Labels added under Projects > Labels section for the current project. |
Issue Owner | Owner (assignee) of the Issue. | LOOKUPLIST | None | Assigned user with access to the current project. |
Issue Priority | Assigning a priority value to an issue. | LOOKUPLIST | None |
Requires Rework, Rejected, On Hold, Open, New
Trivial, Blocker, Critical, Major, Minor OR any custom values added to the “priority“ list within the current project. | ||||
Issue Status | To track the current status of the issue. | LOOKUPLIST | None | Closed, Resolved, Reopened, Open OR any custom values added to the “Issue Status” list within the current project. |
Issue Type | Type of the issue logged - bug, new feature, enhancement. | LOOKUPLIST | None | Bug, New Feature, Enhancement OR any custom issue type value added to the “Issue Type“ list within the current project. |