An Issue is a record for investigating, coordinating, and resolving a problem. It keeps the problem description, impact, responsibility, and resolution information together and connects the issue to affected product information or resulting change work.
When to use it
- Use it when a problem needs ongoing coordination and follow-up.
- Use it when investigation and resolution must remain connected to the affected engineering context.
Key information
- Problem identity: issue ID, name, description, type, priority, and severity.
- Investigation: business impact, root cause, actions, and work log.
- Resolution: resolutions, progress, and resolution date.
Common relationships
- Affected Item identifies product information involved in the issue.
- Assignee identifies the person or group expected to act.
- Issue – Change Request connects the issue to a proposed change for follow-up.
Working with this record
Record what was observed, connect the affected records, and identify responsibility. Separate the original observation from a root cause determined through investigation. Track actions and resolution information so the team can understand what has been addressed.
Example
Seal Leakage is an Issue linked to Pump P-100 and the affected seal. Investigation identifies the cause, and a Change Request proposes a design improvement. The issue retains the investigation and resolution context.
Choosing the right type
Choose Issue for coordinated problem resolution. Choose Problem Report to record the observed problem as a report, Task for a defined follow-up activity, and Risk for an uncertain event that may happen.
