Auto-organize Imported Requirements
Note
If users enable auto-organization of requirements into a folder hierarchy, the existing folder structure will be overwritten. All existing and newly imported requirements will be reorganized based on the defined hierarchy.
You can auto-organize requirements imported from Jira using a two-level folder structure. This structure depends on the Jira Issue Fields configured from Integration. Any changes to the selected Jira field values are reflected in real time within QMetry.
Use Case: The project admin wants to select specific fields from Jira to organize the imported requirements. It creates the folder structure and arranges the requirements as per the set hierarchy.
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
Note
You can select Jira System or Custom fields to create the folder structure.
If you select only one Jira Issue field, then the system creates single level folder structure under the default folder.
If you update the field value, the requirement auto-organizes in the folder structure as per the modified field values.
The system creates new folders when new values are added to the mapped fields.
The system reorganizes imported requirements when users update the folder hierarchy fields.
The system auto-updates the folders when the existing values of the mapped fields are updated.
If users delete values from the mapped fields, QMetry retains the folder structure until it is manually deleted.
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.
When the user selects cascading fields, QMetry creates folders in the format: Parent Value – Child Value.
If the combined field value exceeds the 255-character limit, the system skips creation of the corresponding folder.
To auto-organize imported requirements, perform the following steps:
Go to Projects and open the Integration tab.
Select the Issue Types to sync as Requirements.
Select the folder where the requirements will be synced.
Click the Jira Field Settings icon to configure folder hierarchy.
You can create:
A two-level folder hierarchy by selecting two fields.
A single-level hierarchy by selecting one field.
No hierarchy by skipping field selection. In this case, requirements will be imported directly into the selected folder.
Map Jira fields to QMetry. This is optional. Mapping Jira custom fields impacts the list of available fields for folder hierarchy.
Select fields to organize imported requirements.
Field 1: Select the desired Jira system or custom field. This will be used as the parent folder.
Field 2: Select an additional Jira field to create a sub-folder under the parent folder.
Click Save.
You can track the structuring of Requirement Folder in the Scheduled Tasks section.
The system automatically creates folders based on the values of the selected fields and organizes the imported requirements accordingly. All newly imported requirements from Jira follow this folder hierarchy based on their field values.
Note
Folders are created only for list values that are linked to imported requirements.
All new requirements from Jira will keep auto-importing into the set folder hierarchy depending on the field values of the requirements.
If you modify the field values, the system moves the entities to the folder structure accordingly.
If the values in the fields are new, a new folder structure is created accordingly.
The new and existing Jira-imported requirements are organized based on the new folder hierarchy.
The older folder structure is preserved unless deleted manually.