• Change Request Number, which is automatically generated.
• Short Description.
• Version Information (Version Found In, Fixed In, Closed In).
• Status, such as Submitted, Reviewed, Approved, Assigned, Fixed, Closed, Not Approved, or Deleted.
• Priority (e.g., 1 represents an urgent change request).
• Category (e.g., Software).
• Classes (e.g., Class 1. Customer Approval Required).
• For each status level, the individuals assigned, date, and whether the date is actual or expected can be stored.
• Detailed description of problem.
• Corrective actions taken to fix problem or implement enhancement.

You can customize change requests to record additional information too. Generated reports can be in a tabular, summary, and detailed format. Wild card characters (e.g., "*core*") and qualifiers (e.g., "<") can be used to query and review change requests entries that meet the criteria you specify.

+1CR supports process management. This ensures that when a file is checked in using +1CM, the problem report number exists and its status allows for check ins.

Using Metrics4Project^TM, problem report metrics including the number of open, closed, and total number of problem reports organized by status, priority, category, class, and longevity can be calculated. Metrics4Project can be run in the background on a daily, weekly, or monthly basis at any time and the output can be imported into a spreadsheet program.

Back To FAQ