Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

Bug Reactivations Excel Report

You can use the Bug Reactivations report to determine how effectively the team is fixing bugs. This report shows the cumulative count of Bugs that the team has reactivated and Bugs that the team has since resolved, for the most recent four weeks. The reactivation rate is also referred to as the fault feedback ratio.

For information about how to access this chart, see Excel Reports (Agile).


You can view the Bug Reactivations report from the Quality dashboard. You can access this dashboard only if your team project portal has been enabled and is provisioned to use Microsoft Office SharePoint Server 2007. For more information, see Access a Team Project Portal and Process Guidance.

Required Permissions

To view the report, you must be assigned or belong to a group that has been assigned the Read permissions in SharePoint Products for the team project.

To modify or customize the report, you must be a member of the TfsWarehouseDataReaders security role in SQL Server Analysis Services. You must also be assigned or belong to a group that has been assigned the Members permissions in SharePoint Products for the team project. For more information, see Grant Access to the Databases of the Data Warehouse for Visual Studio ALM and Managing Permissions.

The Bug Reactivations report shows an area graph of the number of Bugs that the team has reactivated (Reactivated and Still Active) from a resolved or closed state and Bugs that the team has Resolved.

Bug Reactivations Excel Report

This report is based on a PivotChart report that shows the most recent four weeks of data that was captured for Bugs and that is stored in the data warehouse.

Required Activities for Tracking Bugs

For the Bug Reactivations report to be useful and accurate, the team must perform the following activities:

  • Define Bugs.


    For information about how to define area and iteration paths, see Create and Modify Areas and Iterations.

  • Update the State of each Bug as the team fixes, verifies, closes, or reactivates it.

  • (Optional) Specify the Iteration and Area paths of each Bug if you want to filter by those fields.

You should expect the Bug Reactivations report to vary based on where you are in your product development cycle. Early iterations should show very few reactivations. As the team closes Bugs, you will want to review the rate of reactivations.

The Reactivations report displays information that you can use to detect whether the team is reactivating a high number of Bugs or User Stories. The reactivation rate counts the number of supposedly fixed Bugs whose fixes do not work. These reactivations can create a harmful cycle of rework that interferes with making progress on planned tasks.

You can review the report to answer these questions:

  • How many Bugs have been reactivated in the past four weeks?

  • Is the team resolving and closing reactivated Bugs quickly enough?

For information about healthy and unhealthy versions of the report, see Reactivations Report.

You can update the Bug Reactivations report by opening it in Office Excel and changing the filter options for the PivotTable report. You can customize this report to support other views as the following table describes.



Reactivation of Bugs for an iteration

Change the filter for Iteration (default=All)

Reactivation of Bugs for a product area

Change the filter for Area (default=All)

Reactivation of Bugs for the last six, eight, or more weeks

In the Columns PivotTable Field List, replace @@Last 4 weeks@@ with a different Set

For more information about how to work with and customize PivotTables and PivotChart reports, see the following pages on the Microsoft Web site:

Community Additions

© 2015 Microsoft