Defect status


The old navigation will be removed from Jira Align in version 10.127.1.
Learn more about the upcoming changes

About this report

The defect status report displays the overall progress of defects for each day contained within the sprint. This line graph is especially useful to both Scrum Masters and product owners, who are seeking an unobtrusive approach to appraising the status of product quality as the sprint evolves.

The line graph generated is a snapshot of counted defects, by day, in each of the following four categories: Active Defects, Closed Defects, Opened Defects, and High & Critical.

Each category is plotted on an X and Y axis, where X represents the date of the count, and Y represents the number of defects counted in the category. 

This report may be beneficial as a tool during daily stand-ups or during sprint review meetings as a mechanism for discussion.

To navigate to this report:

If you’re using the new navigation:

  1. Select Teams in the top navigation bar and select the team you want to view information about.
  2. On the sidebar, select Reports in the list of page options.
  3. Select Defect status; the report displays.

If you’re using the old navigation:

  1. Select the Reports icon from the left Navigation menu.
  2. Start typing the report's name in the Search box.
  3. Once found, select the report.
    Note: You can also use the categories on the left to search for the needed reports.


  1. PI must exist in the system, and be tied to a program. 
  2. Defects must be created and tied to a sprint. 

How are report values calculated? 

  1. Closed Defects = the count of closed defects by date
  2. Opened Defects = the count of opened defects by date
  3. Active Defects = the cumulative count of active defects by date
  4. High & Critical = the cumulative count of high & critical defects by date
  5. Vital Statistics "Accumulating Defects Per Day" = Cumulative Defects / # of days in sprint


How to interpret this report

This report is a quick way to appraise the quality of the teams production mid-sprint. Generally speaking, 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 two lines oscillating between open defects and closed defects.

However, organizations undertaking a quality initiatives may often display graphs such as the example above. In this case, the cumulative number of active defects as well as high & critical defects is climbing, despite the team's efforts to close defects pulled from the backlog.

Was this article helpful?
0 out of 0 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

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.