About this report
The Defects by Priority report displays counts of critical, high, medium, low defects at daily intervals within a selected sprint. The graph is in the form of a stacked bar chart, with defect counts on the y axis and daily intervals on the x axis. Each priority is represented by a specific bar color, defined in a legend at the bottom of the graph.
This report can be used by Scrum Masters, team and QA managers, and QA/development staff to track defects during a sprint. It is beneficial to review the report with team members during daily standup and sprint review meetings.
- Select the Reports icon from the left Navigation menu.
- Start typing the report's name in the Search box.
- Once found, select the report.
Note: You can also use the categories on the left to search for the needed reports.
- PI must exist in the system and be tied to a program.
- Sprints must be created and tied to a PI.
- Teams must be created and tied to a program.
- Stories must be created and tied to a sprint.
- Defects must be created and tied to stories.
How are report values calculated?
- Defect counts (sums), and priority (critical, high, medium, low) are all pulled from the Defects Grid/New Defect panel.
How to interpret this report
This report is a quick way to appraise the quality of the product mid-sprint. Critical/high defects are the most severe and should be remedied first. It is not unusual for a few low-priority, cosmetic defects to remain open at the end of a sprint, as long as all of the critical/high defects have been resolved. Spotting the trends early can help planning for future sprints and PIs.