Poor ticket management can cause missed SLA deadlines, duplicate troubleshooting, incorrect escalations, poor customer experience, loss of important evidence, confusion during major incidents, audit failures, weak handovers between teams, engineering teams receiving incomplete information, security incidents being incorrectly prioritised, and problems being closed without actually being resolved.
If a troubleshooting step, customer decision, configuration change, escalation or workaround is not documented in the ticket, another engineer may have no way of knowing that it happened. For this reason, ticket management should not be treated as administration — it is part of engineering.
Learning Objectives
By the end of this module, you should be able to:
- Understand why ticketing systems are critical to enterprise IT, and navigate the concepts behind ServiceNow, Jira and Zendesk.
- Distinguish incidents, problems, changes and service requests, and understand SLAs and response targets.
- Determine priority using impact and urgency, and distinguish priority from technical severity.
- Write professional ticket descriptions and produce clear investigation updates.
- Document timestamps, correlation IDs and evidence, and protect sensitive information in tickets.
- Escalate incidents effectively and create Engineering-ready bug reports.
- Conduct basic root cause analysis, and understand workarounds versus permanent fixes.
- Maintain major incident timelines and perform global follow-the-sun ticket handovers.
- Write useful closure notes and understand support metrics such as MTTR and SLA compliance.
- Understand how monitoring, SIEM and automation integrate with ticketing systems.
Most importantly: if another engineer cannot understand what happened by reading your ticket, the ticket is incomplete. A technically correct fix combined with poor documentation creates operational risk.
This Module's Lessons
Work through these in order — each builds on ideas from the last. Every lesson has its own "Mark lesson complete" button; your progress across all six is tracked below.
Tickets & Ticketing Platforms
What a ticket is, why companies use ticketing systems, and how ServiceNow, Jira, Jira Service Management, Zendesk and legacy platforms differ.
ITIL Concepts, SLAs & Priority
Incident vs problem vs change vs service request, response vs resolution SLAs, and how priority is actually impact plus urgency — not customer volume.
Writing & Managing Tickets
Ownership and avoiding ticket ping-pong, escalations that read as a story, timestamps and correlation IDs, and handling evidence and sensitive data.
Root Cause Analysis
Symptom vs root cause, the Five Whys, root cause vs trigger, corrective actions, workarounds vs fixes, and writing tickets people can actually search for.
Handover, Closure & Metrics
Escalation types, major incidents and duplicates, security/vulnerability/change tickets, follow-the-sun handover, closure notes, and support metrics.
Labs & the Ticket Queue Simulator
Twelve hands-on labs, the final ticket checklist, and a capstone ticket queue simulator that pulls together logs, PowerShell, troubleshooting and communication.