Product Feedback / Enhancement Request – Problem ↔ Change Integration

[LuanneI]

We’d like to provide feedback on the integration between Problem Management and Change Management and share a use case where the current model creates a gap in traceability.

In our operating model, problem records are owned by problem coordinators, who manage the lifecycle and assign root cause investigation tasks to the appropriate support teams. Those support teams may ultimately implement a fix that requires a change record.

Today, while a change can be opened from a problem record, there is no supported way to relate an already closed change back to the originating problem. This limits our ability to maintain end‑to‑end traceability between problem identification, remediation, and implementation.

Ideally, changes would be opened directly from the problem record. However, in practice, our change records require detailed technical and implementation information that only the implementing team can provide—not the problem coordinator. As a result, changes are often created independently, and once closed, cannot be formally associated back to the problem.

We’d like to explore whether there are options or planned enhancements to support this model, such as:

• Allowing a problem record to be related to an existing (including closed) change
• Supporting a post‑implementation association between change and problem
• Enabling a lightweight placeholder or handoff mechanism that preserves integration without requiring the coordinator to author the full change

Our goal is to preserve strong integration between Problem and Change Management while aligning with real‑world ownership and implementation responsibilities, and without sacrificing reporting, auditability, or lifecycle traceability.

If anyone has feedback on how to make this successful please reply, thanks.