| Table of Contents | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Note |
|---|
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.
Global Filters
You can apply unified filters for project, release, cycle, start date, end date, issue priority, and issue type across all issue analysis reports using the global filters.
...
Issue Summary
You can generate the following types of reports to view Issue Summary. You can find the corresponding filters in the Filters menu.
...
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.
...
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 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.
...
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.
...
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
Filter Report:
Click on the Filter icon on the individual chart to generate the report as per requirement by applying multiple filters.
...
Lower Environment: This can be referred as testing in Previous Environment. For example, build deployed on a staging environment before production.
Higher Environment: This can be referred as testing at Current Environment which will be in sequence of previous one. For example, build deployed on production environment.
...
Resolved Issue Verification
The report shows resolved issues as per the resolved status of issues. For Jira-integrated projects, this report shows the resolved issues based on their resolved status in Jira. The created and resolved date from Jira are shown in the report.
For Azure and Rally integration, this report shows the resolved issues depending on the relevant "Default Resolved Status" in the project settings. Configure Resolved status for issue from Managing Projects, Releases and Cycles.
When multiple projects with different Resolved status configurations are selected to generate the report, it displays issue records for respective projects accordingly.
...
The report considers issues linked to test step/test case during execution as well as issues directly linked to test case from the Issues tab of test case details page. The report displays the details of test suites/test cases associated to resolved issues.
...
Filter Report:
Click on the Filter icon on the individual chart to generate the report as per requirement by applying multiple filters.
...
Issue Average Aging
The report is a bar chart that shows the average age of unresolved issues at a given point of time. The report is generated in accordance with the selection of Project, duration and issue filter.
...
Another issue is created on 2nd May. Now on 4th May there are total 2 issues in Unresolved state with Sum of Unresolved Age 6 days (4 days for Issue1 + 2 days for Issue2).
The report shows the average age of issues on that particular date.
...
Filter Report:
Click on the Filter icon on the individual chart to generate the report as per requirement by applying multiple filters.
...