osTicket - Ticket Lifecycle: Intake Through Resolution

This tutorial outlines the lifecycle of a ticket from intake to resolution within the open-source help desk ticketing system osTicket.

Environments and Technologies Used

• Microsoft Azure (Virtual Machines/Compute)
• Remote Desktop
• Internet Information Services (IIS)

Operating Systems Used

• Windows 10 (21H2)

Ticket Lifecycle Stages

• Intake
• Assignment and Communication
• Working the Issue
• Resolution

Lifecycle Stages

Intake: This is where the ticket is first created.

• Source: Tickets can come in via email, web portal, phone (entered by staff), or API
• Initial Capture: The system records details like subject, description, requester info, department, and priority
• Ticket Number: A unique ID is assigned so it can be tracked
• Auto-Response: The customer usually gets an acknowledgment email confirming receipt

To create a ticket, users must access the ticket portal and log in if required. Once inside, they can submit a request and provide details about their IT-related issue.

---

Assignment and Communication: Once a ticket exists, it needs to be directed and clarified.

• Assignment: The ticket is routed to the correct department or agent. This can be done automatically (via rules/filters) or manually by staff
• Prioritization: Staff may adjust urgency/priority levels (e.g., low, normal, high, emergency)
• Communication: Agents may reach out to the requester for clarification, additional details, or updates. Internal notes can also be added for team collaboration.
• Visibility: Everyone involved can see the history of communications and actions taken.

Once a ticket is created, it is assigned to the appropriate department or agent, with priority levels adjusted as needed. During this stage, agents communicate with the requester for clarification, share updates, and use internal notes to ensure team collaboration and visibility.

---

Working the Issue: This is the active problem-solving stage.

• Investigation: Agents analyze the problem, replicate issues if needed, and look for solutions
• Collaboration: The ticket may be transferred, escalated, or collaborated on with other teams
• Progress Tracking: Status changes reflect movement (e.g., Open → In Progress → Awaiting Reply)
• Customer Updates: The requester is kept in the loop via replies or status changes

In the working stage, agents actively investigate the issue, collaborate with other teams if needed, and track progress through status updates. The requester is kept informed throughout the process with regular communication and updates.

---

Resolution: The ticket reaches closure when the issue is handled.

• Solution Delivery: The agent provides the resolution, instructions, or fix.
• Verification: The requester may confirm if the solution works.
• Closure: The ticket status is changed to Closed or Resolved.
• Post-Resolution Actions: Some setups include customer satisfaction surveys or feedback collection. Reports can also be generated for metrics (e.g., average resolution time).

In the resolution stage, the agent delivers the fix or instructions and confirms the issue is resolved. The ticket is then closed, with optional follow-up actions like feedback surveys or reporting for performance metrics.

Summary

• Ticket Creation – User submits an issue via email, chat, or self-service portal
• Categorization & Prioritization – The issue is assigned a priority level (Low, Medium, High, Critical)
• Assignment to a Technician – A help desk professional works on the ticket
• Troubleshooting & Resolution – The problem is diagnosed and fixed
• Ticket Closure – Once resolved, the ticket is marked closed (with documentation if needed)
• Follow-up & Feedback – User confirms resolution and may provide feedback

Closing Thoughts

Ticket management protocols can vary across different work environments. Some teams may have quotas for resolving a set number of tickets within a given timeframe, while others prioritize tickets based on urgency or impact. By building osTicket from the ground up, I gained a clear understanding of how tickets are handled in an IT role.