Map Jira Work Items to QMetry Modules
When you map a Jira project to a QMetry project, you decide which Jira issue types flow into which QMetry module. Stories and epics typically map to the Requirements module, and bugs and tasks map to the Issues module.
This page describes the rules and constraints for assigning Jira issue types to QMetry modules. For the project mapping procedures, see Map a single Jira project and Map multiple Jira projects and instances.
Note
You configure this mapping while you map the Jira project. Map at least one work item to the Requirements module or the Issues module before you save.
Requirements Module
Map a Jira issue type to the Requirements module when you manage that work as a requirement, such as an epic or a story.
If you manage requirements in Jira as epics, stories, or sub-tasks, select these issue types to link them to the Requirements module.
You can select and map multiple work items, because the Jira work item field is a multi-select list.
Folder selection is mandatory. QMetry imports all matching issue types into the folder you select on the first sync, and syncs all new stories and epics into the same folder. You can move the imported items to other folders later.
Issues Module
Map a Jira issue type to the Issues module when you manage that work as a defect, such as a bug or a task.
To sync Jira bugs or tasks, map the Jira issue type to the QMetry Issues module.
This is also a multi-select configuration.
Work items synced from Jira appear in the QMetry Issues module with an external key that references the Jira work item key.
Mapping Constraint
You can map a Jira issue type to either the Requirements module or the Issues module, but not to both. To change which module an issue type maps to, see the change-mapping behavior in Track and manage synced data.
Save the Mapping
Once you map the Jira issue types to the QMetry modules, select Save and Activate. For an existing Jira integration, select Update.