About this report
The Program Increment Defect Trend and Sprint Defect Trend reports display daily counts of active, high and critical, opened, and closed defects for a selected sprint within a PI. Use these reports to track opened versus closed defects in a sprint, as well as total active defects and critical/high defects per day.
These reports 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 reports 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), states (opened, closed, active, etc.), and severity (critical, high, medium, low) are all pulled from the Defects Grid/New Defect panel.
How to interpret this report
The graph displays the following four lines:
- The blue line shows total count of active defects, plotted per day over the course of the sprint.
- The black line shows the total count of defects closed on each day over the course of the sprint. This value is expressed as a negative number.
- The green line shows the total count of defects opened each day over the course of the sprint.
- The orange line shows the total count of critical and high active defects, plotted per day over the course of the sprint.
At the bottom of the graph, click the checkbox next to any of the lines listed above to toggle its display on the graph.
These reports are a quick way to appraise the quality of the product mid-sprint. Generally, defects found mid-sprint should be rectified as soon as found, or at least by the close of the sprint. Ideally, this should result in a low number of active defects, with most or all defects being closed. 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.
Join the Atlassian Community!
The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.
Need to contact Jira Align Support? Please open a support request.