Sub-task Traceability

The “Sub-tasks” issue type can be synced either with the Requirements module or the Issue module while integrating Jira.

If a sub-task is converted to a parent issue, its linkages as a sub-task in QMetry will be removed. It will be synced as per the configuration done for the respective issue type.

When Sub-task is synced with QMetry Requirement module

Users can import and sync Jira sub-tasks/sub-defects/custom sub-issue types as Requirements. If the Sub-task issue type is synced with the Requirement module, then the Sub Task Issues tab in the requirement details page displays sub-tasks that are linked to that requirement.

Parent Key, Parent Issue Type, and Parent Summary columns are added to the requirement grid view for better traceability of sub-tasks.

Steps:

Step 1. Open the requirements imported from Jira.

Step 2. Open the Sub Tasks Issues tab on the requirement detail page. The stories having child issues (subtasks) are shown in the tab.

When a Story having a subtask is converted into an Epic, its relationship with the issue still remains. The subtask will be shown under the “Issues in Epic” section.

Step 3. Click on the Entity Key to view further details.

Sub-task detail view

The Details tab displays the relationship of the subtask with its parent through the parent issue key, parent issue type, and parent summary.

When Sub-task is synced with QMetry Issue module

Users can import and sync Jira sub-tasks/sub-defects/custom sub-issue types as issues in the Issue Module. If the Sub-task issue type is synced with the Issue module, then the Sub Task Issues tab in the issue details page displays sub-tasks that are linked to that issue. This Sub Task Issues tab shows all subtasks contained in the respective entity. Similarly, on the detail view of a subtask, parent info with Key and Summary is displayed.

The Parent Key column is added in the Issue module grid view to find the parent of subtasks easily.

Steps:

Step 1. Open the issues imported from Jira.

Step 2. Open the Sub Task Issues tab. Bugs having child issues (subtasks) are shown in the Sub Tasks Issues tab.

Step 3. Click on the Entity Key to view further details.

Sub-task detail view

The Details tab displays the relationship of the subtask with its parent through the parent issue key, parent issue type, and parent summary.

When Subtasks are mapped to the Issue module, users can create Jira sub-tasks/sub-defects/custom sub-issues directly from QMetry.

You can search for the required Parent Entity using Key or Summary and select it while creating a new sub-task.

Generate Advance Query Report

Users can generate reports to view the data related to sub-tasks and their parents.

The extParentID field is added in the Requirement and Issue table to make it easier for users to generate reports for data relating to Subtask and its parent.

Sample Query

SELECT child.extKey as "External Key", child.entityKey as "Entity Key", child.summary as "Summary", child.issuetype as "Type",
COALESCE(rparent.extKey, iparent.extkey) as "Parent ExtKey", COALESCE(rparent.extEntityTypeName, iparent.issuetype) as "Parent Type"
FROM issues AS child
LEFT JOIN issues AS iparent ON child.extParentID=iparent.extEntityDataID
LEFT JOIN requirements As rparent on child.extParentID=rparent.extEntityDataID
WHERE child.projectID IN (`@filter.project requirements`) and child.extParentID != "null"