Skip to content

This tutorial walks you through the entire lifecycle of a ticket, from initial intake to final resolution, within the open-source help desk ticketing system, osTicket.

Notifications You must be signed in to change notification settings

samaankw/ticket-lifecycle

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

5 Commits
 
 

Repository files navigation

Disk Sanitization Steps

osTicket - Ticket Lifecycle: Intake Through Resolution

Part 3 of this three-part osTicket tutorial series focuses on the ticket lifecycle, guiding you through the entire process—from ticket creation and intake to resolution—within the open-source helpdesk ticketing system, osTicket. This section demonstrates how tickets are managed, assigned, and resolved efficiently using the platform’s built-in features.

Environments and Techologies Used

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

Operating Systems Used

- Windows 10(21H2)

Ticketing Lifecycle Stages

- Intake - Assignment and Communication - Working on the Issue - Resolution

Stage 1: Intake - Creating a Ticket

Open osTicket to begin creating a new support ticket.

If you need help with the initial setup, refer to Part 1 of this tutorial series

For configuration guidance, check out Part 2 of the series.

Once you're in the system, click on Open a New Ticket and fill out the form with the following details:

Email Address: johnson@osTicket.com

Name: Keyana Johnson

Help Topic: Select Business Critical Outage from the dropdown menu

Issue Summary: The Entire mobile online banking is down

Details: Customers are reporting they are getting a 404 error when attempting to access online banking

After completing the form, click Create Ticket to submit the issue.

Disk Sanitization Steps

Disk Sanitization Steps

Step 2: Assignment and Communication

Log in to osTicket as an Agent using the credentials we created earlier for jane.doe.

Once you're signed in, navigate to the Tickets section and locate the ticket that was created in Step 1. Click on the ticket to open and view its details.

Disk Sanitization Steps

Since this is a business-critical incident, update the ticket with the following details:

Priority: Set to Emergency, as mobile online banking downtime can result in significant revenue loss.

Assigned To: Jane Doe

SLA Plan: Select SEV-A, given the severity and urgency of the issue.

Department: Assign to System Administrators, as they are responsible for the mobile banking infrastructure.

In the Response text box, enter the following message:

"Coordinating with the System Administrators team to bring mobile banking back online."

Once everything is filled out correctly, click Post Reply to update the ticket and begin resolution efforts.

Disk Sanitization Steps

Disk Sanitization Steps

Step 3: Working the Issue

Behind the scenes, Jane is actively collaborating with the Systems Administration team to investigate and resolve the issue as quickly as possible.

Stage 4: Resolution

Once the issue has been resolved, return to the ticket to update the end user.

In the Response text box, enter the following message:

"Jerry from the Systems Engineering team identified and reconnected a failed load balancer. Mobile banking services should now be fully restored."

Update the Ticket Status to Resolved, then click Post Reply.

Since the issue has been addressed, the ticket will automatically move to the Closed tab.

Disk Sanitization Steps

Disk Sanitization Steps

Congratulations! You have created and resolved your first ticket! You have completed the third and final part of this three-part osTicket Install/Configuration/Ticket-Creation tutorial series.

About

This tutorial walks you through the entire lifecycle of a ticket, from initial intake to final resolution, within the open-source help desk ticketing system, osTicket.

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published