Auto-organize Imported Requirements

Users can auto-organize requirements imported from Jira. A two-level folder structure can be created to organize the imported requirements based on the selected Jira Issue fields under project settings (Projects > Integration). Any changes in the values of the selected Jira fields are reflected automatically in real time within QMetry.

Use Case: The project admin wants to select specific fields from Jira to organize the imported requirements effectively. It creates the folder structure automatically and arranges the requirements as per the set hierarchy. It allows users to maintain a structured and organized repository of requirements within QMetry, and track the changes easily.

For example,

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

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.

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.

2. Open the Integration tab.

3. Select the Issue Types to be synced as Requirements. This is a mandatory step.

4. Select the QMetry folder in which the Requirements will be synced. This is a mandatory step.

5. Click on the Jira Field Settings icon.

6. The Edit Jira Fields Configuration screen opens.

You can create a two-level hierarchy of folders by selecting two fields. However, you can also opt to have a single hierarchy by selecting one field or just skip the field selection to import the requirements directly into the folder selected while mapping with the Requirement module.

6(a) Select the Jira fields (custom/system) to be mapped to QMetry. This is an optional step. Mapping of Jira custom fields affects the listing of custom fields for hierarchy.

6(b) Select fields to organize imported requirements. The custom fields in Field 1 and Field 2 populate as per the mapping of custom fields above.

Field 1: Select the desired Jira Issue field (system/custom) in the drop-down list. It will be the parent folder in the folder hierarchy.
Field 2: Additionally, you can select the desired Jira Issue field (system/custom) in the drop-down list. It will be the sub-parent folder in the folder hierarchy.

7. Click Save.

The folder hierarchy will be created as per the field selection.

You can see the Restructure of Requirement Folder progress in the Scheduled Tasks section.

Folders will be auto-created based on the values of the selected fields. The imported requirements are organized in these created folders based on the values associated with them.
All new requirements from Jira will keep auto-importing into the set folder hierarchy depending on the field values of the requirements.

Note: Folders will be created only for those list values that are associated with any of the imported entities.

If the field values are modified later, the entity will be moved to the folder structure accordingly. If the values in the fields are new, the folder structure will be created accordingly.

The new and existing Jira-imported requirements will be organized based on the new folder hierarchy. The older folder structure will be preserved unless deleted manually.