Ticket Classes

Automate your ticket business processes by configuring your ticket classes, in order to better manage all work related to your ongoing services, save time and increase the quality of your work.

Using this guide, you can:



 

Ticket Classes

Your Accelo deployment came with a basic set of Ticket class options to help you classify the symptoms or characteristics of a Ticket.

An admin user will be able to modify the list of classes for all Tickets.

To view a list of classes:

  1. Click the Modules button.

    accelo.ModulesButton12 
  2. Select Configuration.

    accelo.Configuration9 
  3. Select Tickets and choose Classes.

    accelo.TicketsClasses 

From the Ticket Class list, view the number of Tickets that match each class. Refer to the columns to see the number of SubmittedOpenResolved and Closed Tickets in each class. These are the default system statuses.

accelo.TicketsClassNumbers 

If you click a number, you will now be viewing a list of Tickets matching that class and its underlying status.
 

To add a new ticket class:

  1. Click the Add Class button.
    Ticket Class 
  2. Enter all class details:

    * Parent: Select a parent class if you would like this class to be dependent on another.

    * Status: Select whether this class should be active or inactive.

    * Description: Brief description of the new Ticket class, for internal records.

  3. Click Save.

 

To delete a class:

  1. Click on the class in the Ticket Class list that you wish to delete.
     
  2. On the Edit Ticket Class screen, click the Delete Class button. 

Note: If there are Tickets currently using a class, you will not be able to permanently remove that class.
 

To edit a class:

  1. Click the name of the class.

    accelo.TicketsClassName 
  2. Edit any class details.

To create a child class:

  1. Click the + button next to the parent class.

     
  2. Follow the instructions above to Add a Class.
Accelo uses cookies to give you the best possible experience - by clicking 'Continue' you agree to our use of cookies. Refer to our Privacy Policy for details. Continue