Issue Leakage Rate and Issue Average Aging Reports will not display data for QMetry Projects that are synced with Jira Project, as these reports can be viewed directly in Jira.

Introduction

Issue Analysis reports can be generated for multiple projects. You can view the details pertaining across project.

Project: Select project to generate the report for. Users can select more than one project on the list.
Release: Select either one release or "All" to consider all the releases on the list. Cycles on the graph will be shown based on the release selected here.
Date Range: Provide Start Date and End Date either directly typing in the field or using the calendar to define the duration.
Select Issue Priority and Issue Type to consider while generating the report.

Click on the Search button.

Issue Summary

You can generate the following types of reports to view Issue Summary. You can find the corresponding filters in the Filters menu.

Issue Summary by Workflow Status: The report shows issues by their workflow status i.e. the value in the Status field of issues.
Issue Summary by Priority: The report shows all Issues organized by priority.
Issue Summary by Type: The report shows issues categorized by type.This is the Type mentioned while creating an issue/logging a bug.
Issue Summary by Assignee: The report shows all issues organized by their assignee - either QMetry Owner or Jira Assignee.

You can drill down the chart to view details in tabular format.

Issue Summary by Workflow Status

Issue Summary by Priority

Issue Summary by Type

Issue Summary by QMetry Owner/External Assignee

Filter Report:
Click on the Filter icon

on the individual chart to generate the report as per requirement by applying multiple filters.

Issue Count by Status & Priority

As the name suggests, the report gives count of issues by Status and Priority assigned to them. The legends are provided below the graph.

The legends are clickable. You can hide/show Priority displayed on the graph by clicking on the corresponding priority.

Users can drill down the chart to view details in tabular format.

Filter Report:
Click on the Filter icon

on the individual chart to generate the report as per requirement by applying multiple filters.

Issue Velocity Compared to Test Cases Executed

The report displays the velocity of logged Issues vs. Executed test cases during a particular Cycle. The management gets the visibility of bugs logged in proportion to the execution.

The X-axis displays Cycles of selected Release(s).

The Y-axis displays count of logged Issues and count of Executed Test Cases.

Archived records will be excluded from the report.

Users can drill down the chart to view details in tabular format.

Filter Report:
Click on the Filter icon

on the individual chart to generate the report as per requirement by applying multiple filters.

Issue Velocity Compared to Requirements

The report displays the velocity of number of Issues logged during the cycles vs. number of requirements associated to the release and cycles. The count of logged issues includes distinct count of issues logged to requirements and issues logged during test execution.

The report helps Managers make Release planning by knowing the velocity of issues vs. number of stories.

The X-axis displays Cycles of selected Release(s).

The Y-axis displays the count of Requirements and issues logged for Test cases and Requirements for selected release.

Users can drill down the chart to view details in tabular format.

Filter Report:
Click on the Filter icon

on the individual chart to generate the report as per requirement by applying multiple filters.

Issue Leakage Rate

The report shows Issue Leakage (in percentage) between previous environment and current environment. Bugs/Defects missed from one level of testing to next level of testing is called Issue Leakage. Issue Leakage is the presence of bugs/defects which can be detected in the earlier stage of testing. The report helps QA Manager know the defect leakage and keep check on it.

Users can drill down the chart and can find all Production Environment issues.

Issue Leakage is calculated as below:

Number of Issues found during next phase / (Number of Issues found during testing + Number of Issues found during next phase) * 100