Skip to content

CollinsU99/ticket-lifecycle

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

5 Commits
 
 

Repository files navigation

osTicket logo

osTicket: Post-Install Configuration

This lab provides a step-by-step guide to 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
  • osTicket

Operating Systems Used

  • Windows 10 Pro (22H2)

Ticket Lifecycle Stages

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

Lifecycle Stages

img

We will create some tickets as end users and solve those tickets as a helpdesk support professional.

Paste this link (end users osTicket url): http://localhost/osTicket/ in your VM's web browser and click Enter.

On the osTicket support center page, click "Open a New Ticket".

img

Fill in Karen's information as shown in the image above. Select "Business Critical Outage" for Help Topic. Add an issue summary with more explanation, and click "Create Ticket".

img

The ticket has now been created.

We will create a couple more tickets. Click the "Open a New Ticket" tab.

img

Let's create one as Ken. Fill in the information as shown in the above image, select a help topic, and write the issue summary. Click "Create Ticket

img

Let's create one more ticket as Karen. Create the ticket as shown in the image above.

img

We will now login into osTicket as a help desk support professional to try an solve the tickets

Go to: http://localhost/osTicket/scp/login.php

We will login as Jane Doe, as shown in the image above.

img

It seems like Jane Does doesn't have permission to solve tickets. Let's log out and log in as admin so we can make some changes to Jane's account and allow her to solve tickets.

Click Log Out at the top left of the page.

img

Log in as admin, as shown in the image above.

img

Click on the "Admin Panel" tab at the top right of the page.

img

Click "Agents".

img

Click "Jane Doe".

img

Click the "Access" tab, add Jane Doe to "Support", select "Supreme Admin", and click "Save Changes". Click log out at the top right of the page.

img

Let's log back in as Jane Doe.

img

Jane Doe is now able to see the tickets we created as end users.

Let's observe the tickets and make some changes to them.

img

Click the "Mobile banking is experiencing an outage" ticket.

img

Let's change it's priority. Click "Normal".

img

Change the priority level to "Emergency", and click "Update".

img

Click "Unassigned".

img

Assign it to Jane Doe, and click "Assign".

img

Click "Default SLA".

img

Select "SEV-A", write some notes, and click "Update".

img

Click "Support"

img

Select "System Administrators", write some notes, and click "Transfer".

img

Write some notes, click "Post Reply", and click the "Tickets" tab at the top.

img

As shown in the image above, the ticket has been assigned to Jon Does, and the priority has change.

Let's close the ticket by clicking it.

img

Update the note, select "Closed", and click "Post Reply".

img

As shown in the image above, the ticket is no longer on our list of open tickets.

Let's work on the "Adobe Reader is down" ticket. Click on it.

img

As shown in the image above, change the priority to "High". Assign it to John Wood, and change the SLA to SEV-B.Write some notes and click "Post Reply".

img

Click on the "When are we getting a hardware refresh" ticket.

As shown in the image above, change priority to "Low", assign it to Jane Doe, change SLA to SEV-C. Write some notes, mark it as "Resolved", and click "Post Reply".

img

Now, we only have one ticket left. In order to work on the ticket, we need to sign in as John Wood, since it's assigned to him. Click the "Log out" tab at the top right of the page.

img

Log in as John Wood.

img

Click on the ticket.

img

Update the note. Click "Post Note", and click the "Log Out" tab at the top right.

In order to close the ticket, we need to login as Admin and give John permission to close his own ticket.

img

Let's log in as Admin, so that we can close the ticket.

img

Click "Admin Panel".

img

Move your cursor to the "Agents" tab and click "Departments".

img

Click "Support".

img

Click "Access".

img

Select "Supreme Admin", select "All Access", click "Save Changes", and log out.

img

Let's log back in as John Wood.

img

Open the ticket by clicking on it.

img

Write some notes, select "Resolved", and click "Post Reply".

img

We no longer have any open tickets

img

Click "Closed" to see all our closed tickets.

Congrats, you made it to the end :)

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published