🛠️ Tools & Platforms — Problem Management

ServiceNow Problem Management

Key Features

• Problem Workbench: Unified view of problem record, related incidents, CMDB CIs, and change requests
• Cause Codes & Resolution Codes: Structured classification for trend analysis
• Known Error Portal: Searchable KEDB surfaced to Service Desk agents in incident workflow
• Problem Similarity Detection: ML suggests related problems and known errors at problem creation
• Performance Analytics: Problem age, recurrence rate, and KEDB coverage dashboards

Configuration

Problem Priority Matrix:
  High impact + High urgency = P1 (target: workaround < 24h)
  High impact + Low urgency = P2 (target: workaround < 72h)
  Low impact = P3 (target: resolution < 30 days)

Cause Code taxonomy (recommended):
  - Application defect
  - Infrastructure failure
  - Configuration error
  - Human error
  - Vendor / third-party
  - Security vulnerability
  - Capacity / performance

Workflow Tip

Link the Problem Management module to Major Incident Management — ServiceNow can auto-create a Problem record from a closed P1 incident if the RCA field is populated with "Recurring Issue".

Jira Service Management

Problem Management Project Setup

Project: Problem Management
Issue Types: Problem, Known Error
 
Statuses:
  Open → Under Investigation → Root Cause Identified
  → Workaround Available → Fix in Progress → Resolved → Closed
 
Custom Fields:
  - Root Cause (text)
  - Workaround (text)
  - Related Incidents (linked issues)
  - Fix Change Request (linked change)
  - RCA Technique Used (5 Whys / Fishbone / FTA)

Automation Rules

Rule: Auto-create Problem from recurring incidents
  Trigger: 3 incidents with same category in 30 days
  Action: Create Problem record + link all incidents
 
Rule: Notify Incident Manager of workaround
  Trigger: Workaround Available status reached
  Action: Comment on all linked incidents + notify Service Desk team
 
Rule: Auto-close Problem after fix deployed
  Trigger: Linked Change Request transitions to Closed + verified
  Action: Prompt Problem Manager to close problem

Confluence KEDB

Use a Confluence space as a structured KEDB:

• One page per Known Error using a standardised template
• Link Confluence pages to Jira Problem records
• Use Confluence search for Service Desk agents to find workarounds quickly

SMAX (OpenText)

• Smart Problem: ML correlates incidents to suggest problem creation automatically
• Related Record View: Problem, incidents, changes, and CMDB CIs in one panel
• Analytics Studio: Build proactive trend dashboards showing recurring incident categories
• Knowledge Integration: Auto-suggest KEDB entries from Knowledge module during incident resolution

BMC Helix ITSM

RCA Templates in BMC Helix

Configure structured RCA forms for each problem category:

• 5-Whys template for straightforward problems
• Fishbone template for multi-cause problems
• Timeline template for post-P1 incident analysis

ManageEngine ServiceDesk Plus

• Problem Management module: Full lifecycle from detection to closure
• Incident-to-Problem linking: One-click problem creation from incident with auto-linking
• Root Cause Analysis: Built-in structured RCA form
• Solution & Workaround: Captured in problem record and pushed to knowledge base
• Reports: Problem aging, resolution trends, recurring issue analysis

Freshservice

• Problem Management: Standard ITIL-aligned workflow
• Freddy AI: Suggests similar problems and known errors when creating incidents
• Timeline View: Visual history of all activities on a problem record
• Linked Tickets: View all related incidents, changes, and releases on one screen
• Knowledge Base Integration: Promote resolutions directly to KB from problem closure

Tool Comparison: Problem Management

✅✅ Excellent · ✅ Good · ⚠️ Partial · ❌ Not available

Downloadable Resources

← Back to Problem Management