Configuration Management

• Overview
• CM Tools

Issue Tracking

• Field Summary
• State
• Priority
• Severity
• Issue Type
• Symptoms
• Functional Area
• Resolution
• Target Release

Issue Reports

• Cumulative Trends
• Rolling Totals
• Historical Priority
• Historical Severity
• Project State Distribution
• Project Trends
• Transition Summary
• Staff Workload

Symptoms

Symptoms indicate what the problem is or was, and are useful for developers looking for patterns.

The value of items in a "Symptoms" drop-down may vary from project to project, but will most likely have considerable overlap.  The important thing is that even if the values for symptoms differ, that the definition/purpose remain consistent between all projects.

One of the reasons for a 'Symptoms' field is that 'Severity' is only a single-select field, and often people have a tendency to add more 'Severity' values just to indicate additional information that is more aptly kept in a separate 'Symptoms' field.

Examples of Symptoms:

• GPF
• Spelling error
• slow performance
• access violation
• data loss.

Contact Primary Goals for a detailed review of your issue tracking system, or for consultative assistance to ensure that you have a smooth deployment of your CM system.