1 What Is a Ticket?
A ticket is a structured record representing work that needs to be performed. Tickets may represent incidents, service requests, problems, changes, security incidents, vulnerabilities, access requests, hardware failures, software defects, customer support cases, feature requests, compliance tasks, investigation tasks, or maintenance activities.
Ticket Number: INC0012456
Customer: Example Bank
Reported Issue: Users cannot authenticate to the VPN.
Priority: P1 / Critical
Status: In Progress
Assigned Team: Identity Engineering
Assigned Engineer: John Smith
Created: 10:32 UTC
Last Updated: 10:48 UTC
Affected Service: Corporate VPN
Business Impact: Approximately 4,000 remote employees affected.
Troubleshooting:
- VPN gateway reachable
- RADIUS requests reaching authentication servers
- Authentication servers returning Access-Reject
- Authentication failures started after certificate renewal
Next Action: Validate RADIUS certificate chain.
Related Change: CHG0008742The ticket should allow another engineer to understand the situation without having to start the investigation again — that single sentence is the standard everything else in this module is measured against.
2 Why Companies Use Ticketing Systems
Imagine a company with 100,000 employees, offices in 40 countries, thousands of servers, hundreds of applications, multiple cloud platforms, several security teams, outsourced support providers, and 24×7 operations. Email alone cannot manage that volume of operational work. Ticketing systems provide ownership, accountability, prioritisation, workflow, escalation, SLA tracking, reporting, audit trails, historical records, knowledge management, and automation.
A well-run ticket answers: what happened, who owns the issue, how serious is it, what troubleshooting has already been performed, who has been contacted, what is the next action, when must the next response happen, has the SLA been breached, has Engineering been involved, what change caused the issue, and what ultimately fixed the problem.
3 ServiceNow
ServiceNow is one of the most widely used enterprise IT service management platforms — frequently used for Incident Management, Problem Management, Change Management, Service Requests, Asset Management, Configuration Management, Knowledge Management, Security Operations, Vulnerability Management, and employee workflows generally.
Employee → Service Portal → ServiceNow Incident → Help Desk
→ Infrastructure Team → Identity Team → Vendor SupportServiceNow records typically use prefixed identifiers: incidents as INC0012345, changes as CHG0012345, problems as PRB0012345, and service requests as REQ0012345 — exact conventions vary by organisation. A typical incident lifecycle moves New → Assigned → In Progress → Pending → Resolved → Closed, with organisations customising heavily — a ticket might sit in Pending Customer while waiting on logs, or Pending Vendor once escalated to a third party. Understanding ticket status matters because SLA calculations often depend on it.
4 Jira & Jira Service Management
Jira originated as an issue and software development tracking platform but is now heavily used across engineering, infrastructure, security and business teams. Common ticket types include Bug, Task, Story, Epic, Incident, Change, Feature, and Security Issue. A Jira ticket like AUTH-1842 combines a project identifier (AUTH) with a ticket number (1842).
A customer-reported crash under heavy load might start as a customer ticket (CASE-83922); once support confirms it's a software defect, Engineering opens a linked Jira bug (AUTH-2847). The customer should normally not get unrestricted access to internal Jira — it can contain source code references, internal comments, security-sensitive information, customer names, vulnerability details, and internal engineering discussions. Support's job is to translate Engineering's updates into appropriate customer-facing communication (Module 17 covers exactly this translation skill).
Many companies use Jira Service Management as an alternative to ServiceNow for IT operations — incident queues, request portals, SLA tracking, approvals, automation, knowledge integration, escalation workflows and change management — while using plain Jira Software for Engineering defects.
5 Zendesk, Legacy Systems & Public vs. Internal Notes
Zendesk is common in customer-facing support environments — SaaS companies, technology vendors, consumer technology, online services, cloud companies. Zendesk tickets typically carry customer, organisation, priority, status, tags, assignee, group, public comments, and internal notes.
A public reply says: "We have reviewed the authentication logs and can confirm the request is reaching the authentication server. The server is currently returning an invalid credential response." An internal note on the same ticket says: "Possible regression introduced in 8.7. Symptoms similar to ENG-4821. Need Engineering confirmation before discussing defect with customer." What happens if an engineer accidentally posts the internal note as a public reply?
Reveal the answer
It can expose internal conversations, security concerns, customer information, engineering defect numbers, confidential information, or commercial discussions directly to the customer. Engineers must always verify whether they are writing a public reply or an internal note before submitting — most platforms make this distinction visually obvious (a colour or icon change) specifically because this mistake is so common and so costly.
You will not always work with modern systems. Many organisations — especially banks, governments, and large enterprises — still run older platforms like BMC Remedy, HP Service Manager, CA Service Desk, Lotus Notes databases, SharePoint lists, custom SQL applications, or even email-based ticket systems, because replacing them can be extremely expensive. Never assume old technology means unimportant technology — many legacy systems still process critical infrastructure, and a workflow that looks outdated may be exactly the one nobody can afford to have go wrong.