An issue queue shows the same address defect opened twelve times by different teams. What should structured DQ issue management emphasize?
Select an answer to reveal the explanation.
Short Explanation
Twelve tickets for one bad address is like twelve work orders for the same pothole—noise without progress. Good issue management collapses duplicates and tracks the real defect once. Coordination beats ticket spam.
Full Explanation
Structured DQ issue management identifies, tracks, and resolves defects with clear ownership and status. Duplicate tickets for the same underlying address defect waste effort and obscure true backlog. Deduplicating and linking related reports keeps remediation focused on root issues.