...
Component and Priority fields are selected for Field 1 and Field 2 respectively.
Component values: Sanity, Regression
Priority values: High, Medium, Low
The folder structure will be created as per the values that exist in the field of requirements.
Sanity > High
Sanity > Low
Regression-Sanity > High
Regression-Sanity > Low
| Note |
|---|
If you are opting for auto-organizing requirements in folder hierarchy, your existing organization of requirements in folder structure will be lost. Your existing requirements will also move to the defined folder hierarchy along with the new requirements. |
Notes:
The folder structure can be created by selecting Jira System or Jira Custom fields.
If only one Jira Issue field is selected to organize the requirements folders, then QMetry will have a one-level folder structure under the default selected Imported from the Jira folder.
When the field value of a requirement is updated, the requirement will be auto-organized in the folder structure as per the modified field values.
When the field level selection for folder hierarchy is changed in the project settings, the new and existing imported requirements will be organized as per the new folder structure.
When new values are created for the mapped fields, the folder structure is auto-created.
When the existing values of the mapped fields are updated, the folder structure is auto-updated.
When the existing values of the mapped fields are deleted, the folder structure remains as it is unless deleted manually.
If any of the selected Jira fields' values are changed after the initial import, the imported requirements are reorganized accordingly. For example, if a requirement changes its "Priority" from "High" to "Blocker," it will be moved from the "High" subfolder to the "Blocker" subfolder.
If requirements have more than two values for the hierarchy field, then the folder will be created with a name containing a hyphen in between the two values e.g., Regression-Sanity.
Folders containing Jira Requirements can't be archived and deleted.
| Note |
|---|
If you are opting for auto-organizing requirements in folder hierarchy, your existing organization of requirements in folder structure will be lost. Your existing requirements will also move to the defined folder hierarchy along with the new requirements. |
Steps:
1. Go to Projects > Project/Release/Cycle.
...