Reports Information

The various reports are shipped with PR-Tracker as follows:

Status Summary Report

The Status Summary report provides statistics on the number of open problem reports. The open problem reports are broken down by status and priority.

Work Remaining Report

The Work Remaining report calculates the number of hours required to close all assigned problem reports. The work remaining is summarized according to the tasks of investigation, resolution, and verification and according to priority. Work remaining on problem reports with status new are not included in this report, so it is best if all new problem reports are assigned before generating this report.

Work Remaining Report by User

The Work Remaining Report by User provides a breakdown of the work remaining by each user.

Transaction Log Report

The Transaction Log report is a list of all transactions that have occurred between two dates. Transactions include originating (creating a new), assigning, postponing, investigating, resolving, verifying, failing, closing, and modifying reports.

Each transaction entry lists the date, time, problem report number, transaction, and person performing the transaction. One thing that you can use this report for is to determine what work has been done this week.

Daily/Weekly Transaction Summary

The Daily/Weekly Transaction Summary report provides a summary of the transactions made for each day or for each week.

Daily/Weekly Transaction Summary by Priority

The Daily/Weekly Transaction Summary by Priority report provides a summary of the New and Close transactions by priority made for each day or for each week.

Detection Method Statistics Report

The Detection Statistics report lists how many problems were detected by each test method, and what the priority break down is. This report lets you know which test methods are most effective in detecting errors. If you track the number of hours spent doing each kind of testing you will have a better idea about how effective these methods are.

Bug tracking doesn't have to be complicated | Help | Site Map