jcaines512 / ticket-lifecycle

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

osTicket logo

osTicket - Ticket Lifecycle: Intake Through Resolution

This tutorial guides you through the entire process of handling support inquiries within osTicket, from intake to resolution.

In this tutorial, we will explore the process of working in osTicket as a professional helpdesk technician, efficiently responding to tickets and resolving issues.

Video Demonstration

Environments and Technologies Used

  • Microsoft Azure (Virtual Machines/Compute)
  • Remote Desktop
  • osTicket (Help Desk Ticketing System)

Operating Systems Used

  • Windows 10 (21H2)

Ticket Lifecycle Stages

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

Lifecycle Stages

Stage 1: Intake

Access the portal, sign in, and generate a new customer ticket for testing purposes. The URL: osTicket Link

In this stage, a new ticket is created. Tickets can be submitted through a form or by emailing a designated ticket address. Users provide their contact information, select the topic/issue, and provide details about the problem.

Stage 2: Assignment

After the ticket is submitted, it can be assigned to an IT professional. In our case, the ticket handling information has been adjusted for proper management. The severity level has been updated, with the Priority set to "Emergency," the SLA Plan to "SEV-A," and the Department to "System Administrators." Additionally, the ticket has been assigned to the administrator "Jane Doe" for resolution.

Disk Sanitization Steps

Stage 3: Working the Issue

With the ticket now assigned to the relevant department and staff members, the IT team can begin working on resolving the issue. Throughout the process, any updates or changes related to the ticket can be documented in the Ticket Thread through comments. This ensures that all individuals viewing the ticket are informed about the progress and fosters effective communication among everyone involved.

Stage 4: Resolution

Once the issue has been successfully resolved, the ticket can be closed, causing it to transition from the Open section to the Closed section. As IT professionals, it is beneficial to browse through closed tickets as they serve as a valuable repository of solutions that can be referenced when handling open tickets. Consider it a "big library" of knowledge that aids in addressing future inquiries effectively.


About