What this operation supports in Freshservice
This creates a new problem record, representing the underlying root cause behind one or more related incidents.
Tracking a root cause separately from individual tickets
Use this when multiple tickets trace back to the same underlying issue, so the root cause can be investigated and resolved once rather than per-ticket.
Operational considerations
Linking the related incident tickets to this problem keeps the root-cause investigation connected to the tickets it's actually affecting.
Use cases
Use cases include converting recurring incidents into problems, or creating a problem from an alert in a monitoring system.
- Incident-to-Problem mapping for post-mortem analysis.
- Automated problem creation from threshold breaches.
- Root-cause tracking across related tickets in Freshservice.
- Audit-ready problem records for compliance.