Service Desk Compare ticket stub markService Desk Compare

UNIVERSITY · LESSON 02

Incident, problem and change management: how the three practices connect

Last reviewed 27 September 2026 · Service Desk Compare reviewers

What does each practice do?

Incident management

Get the user working again as quickly as possible. A workaround counts.

Incident management in the glossary

Problem management

Find and remove the root cause of one or more incidents, and record known errors until they are fixed.

Problem management in the glossary

Change enablement

Assess, approve and schedule the change that removes the cause, so the fix is safe.

Change enablement in the glossary

How do they connect in practice?

An illustration, not a real case: several employees report that a shared drive is slow on Monday mornings. Each report is an incident, and agents restore service by restarting a job. When the same incident recurs, someone opens a problem record, links the incidents to it, and finds that a backup job overlaps with the start of the working day. The fix is to move the job, which is a change: it is assessed, approved and scheduled. Once the change is complete, the problem is closed and the incidents stop.

What should you check in a service desk tool?

  • Can an agent link several incidents to one problem record from the ticket view?
  • Does the problem record hold a known error and its workaround, so other agents can reuse it?
  • Can a change be raised from the problem, with the link kept for later review?
  • Does the change workflow include an approval step, for example a change advisory board?
  • Which plan includes each of these? The plan gates lesson lists them by vendor.

Where does configuration data fit?

All three practices lean on the same record of what exists. An incident is faster to route when the ticket names the affected service, a problem is easier to trace when similar incidents point to the same configuration item, and a change is safer when you can see what depends on the item you are changing. That record is the CMDB. Tools that document a CMDB link it to all three practices; tools that do not leave that link to the agent's memory. The CMDB entry in the glossary and the CMDB article in Desk notes go further.

Why are they priced differently?

Because many vendors treat problem and change as advanced practices. On the pages we read on 27 September 2026, Jira Service Management puts change management on Premium [Atlassian pricing], Freshservice puts problem, change and release management on Pro and Enterprise [Freshservice pricing], and ServiceDesk Plus sells them as add-ons on Standard or includes them in Enterprise [ManageEngine pricing]. monday service and Zendesk do not document problem or change management on the pages we read. See what ITSM covers for the full practice table and total cost for what the plan gates mean in money.

Next lesson

How to read a service desk price page

What per agent, billed annually, seat minimums, portal caps, AI add-ons and credits mean on an IT service desk price page, with examples from vendor pages in 2026.
Start the lesson

Lesson

03