A Problem Report captures an observed problem and the information needed to investigate it. It gives the observation its own identity and can connect it to an Issue or Change Request for further action.
When to use it
- Use it when a problem is first reported or needs its own report record.
- Use it to preserve the observed facts and the affected product context before or during investigation.
Key information
- Report identity: problem report ID, name, description, and type.
- Triage: priority, severity, summary, and root cause as investigation develops.
- Follow-up context: owner, state, due date, and comments.
Common relationships
- Affected Item connects the report to the affected product information.
- Problem Report – Issue connects the observation to an issue for coordinated resolution.
- Problem Report – Change Request links the report to a proposed corrective change.
Working with this record
Describe the observation and the conditions in which it occurred. Identify the relevant item or document, and add supporting information. Keep reported facts distinct from investigation conclusions, then connect the appropriate follow-up record.
Example
A Problem Report records leakage observed during prototype testing of Pump P-100. It identifies the affected pump information and links to the Seal Leakage Issue used to coordinate investigation and resolution.
Choosing the right type
Choose Problem Report for the recorded observation. Choose Issue for ongoing coordination of the problem and Change Request for a proposed modification. Linking these records keeps the report, investigation, and proposal understandable.
