Skip to main content

Ticket Management Guide

Tickets are the core of ITSM-NG’s service management system. This guide covers everything you need to know about creating, managing, and resolving tickets efficiently.

Creating a New Ticket

1

Access the Ticket Creation Form

Navigate to Assistance > Create a ticket in the main menu, or use the keyboard shortcut Alt+T.
2

Fill in Basic Information

  • Title: Enter a clear, descriptive subject for the ticket
  • Type: Select either “Incident” or “Request”
  • Category: Choose the appropriate category from the dropdown
  • Requester: Add the user(s) requesting assistance
  • Description: Provide detailed information about the issue or request
3

Set Priority and Urgency

  • Urgency: Rate how quickly the issue needs resolution
  • Impact: Assess how many users or services are affected
  • Priority: Automatically calculated based on urgency and impact
4

Assign and Link Assets

  • Assign to: Select technician, group, or supplier
  • Associated items: Link related computers, software, or other assets
  • Location: Specify the physical location if relevant
5

Submit the Ticket

Click Add to create the ticket. You’ll be redirected to the ticket details page.
Use the keyboard shortcut Shift+P to quickly jump to ticket processing once a ticket is open.

Understanding Ticket Status

Tickets progress through different statuses during their lifecycle:
StatusDescription
NewTicket just created, awaiting assignment
AssignedTicket assigned to a technician or group
ProcessingWork is actively being performed
PendingAwaiting external input or action
SolvedSolution provided, awaiting approval
ClosedTicket completed and closed

Working with Tickets

Viewing Your Tickets

Access different ticket views based on your role:
  • My tickets: Tickets where you’re the requester
  • Tickets to follow up: Tickets you’re observing
  • Assigned to me: Tickets assigned to you
  • Group tickets: Tickets assigned to your groups

Processing a Ticket

1

Open the Ticket

Click on the ticket number to view full details. The timeline shows all activity.
2

Add a Follow-up

  • Click Add a follow-up in the timeline
  • Enter your update or communication
  • Choose whether to notify requesters
  • Set as Public (visible to requester) or Private (internal only)
3

Create a Task

  • Click Add a task for internal tracking
  • Assign the task to a technician
  • Set task duration and status
  • Tasks are always private to technicians
4

Update Status

Change the ticket status as work progresses using the Status dropdown.

Taking Ticket Ownership

If you have the appropriate rights:
  • Click Take to assign the ticket to yourself
  • Or click Assign to assign to another technician or group
You cannot take ownership of closed or deleted tickets.

Adding Solutions

1

Navigate to Solution

In the ticket timeline, click Add a solution.
2

Select Solution Type

Choose from predefined solution types or create a custom one.
3

Enter Solution Details

Provide a clear description of what resolved the issue. This will be visible to the requester.
4

Submit for Approval

Click Add to submit the solution. The ticket status changes to Solved.
Requesters can approve or refuse the solution. If approved, the ticket automatically closes.

Service Level Agreements (SLA/OLA)

Understanding SLA and OLA

  • SLA (Service Level Agreement): External commitment to requesters
    • Time to Own (TTO): Maximum time to assign the ticket
    • Time to Resolve (TTR): Maximum time to solve the ticket
  • OLA (Operating Level Agreement): Internal performance targets
    • Same TTO/TTR metrics but for internal tracking

SLA Indicators

Tickets display SLA information prominently:
  • 🟢 Green: Within SLA targets
  • 🟡 Yellow: Approaching deadline
  • 🔴 Red: SLA breached
Use the SLA countdown to prioritize your work and meet service commitments.

Ticket Validation

For tickets requiring approval:
1

Request Validation

Add validators when creating or updating the ticket in the Validation tab.
2

Validator Reviews

Validators receive notifications and can:
  • Approve the ticket
  • Refuse with comments
  • Request more information
3

Track Validation Status

View validation progress in the Validation tab.
  • Duplicate: Mark as duplicate of another ticket
  • Related to: Associate related tickets
  • Parent/Child: Create hierarchical relationships
Convert solved tickets into knowledge base articles:
1

Open Solved Ticket

Navigate to a ticket with an approved solution.
2

Create KB Article

Click Convert to Knowledge Base to create an article from the solution.
3

Configure Visibility

Set who can view the article (users, groups, profiles, entities).

Ticket Statistics

View ticket metrics and performance data:
  • Statistics tab shows resolution time, response time, and other KPIs
  • Processing ticket tab displays the complete timeline
  • Costs tab tracks time and material costs associated with the ticket

Advanced Features

Recurring Tickets

Create tickets that automatically generate on a schedule:
  1. Navigate to Assistance > Recurrent tickets
  2. Define the template and schedule
  3. Set start and end dates for recurrence

Ticket Templates

Use templates to standardize ticket creation:
  • Predefined fields: Auto-populate common values
  • Mandatory fields: Ensure required information is provided
  • Hidden fields: Simplify the form for specific categories

Email Integration

Tickets can be created and updated via email:
  • Send emails to your configured helpdesk address
  • Replies to ticket notification emails update the ticket
  • Attachments are automatically added as documents
Self-service users can only update tickets if they have no follow-ups or tasks, and the ticket is not solved or closed.

Satisfaction Surveys

After ticket closure, requesters may receive satisfaction surveys:
  • View survey results in the Satisfaction tab
  • Surveys expire based on entity configuration
  • Ratings help measure service quality

Best Practices

For Requesters:
  • Provide detailed descriptions including error messages and screenshots
  • Check existing tickets to avoid duplicates
  • Respond promptly to technician questions
  • Test and approve solutions quickly
For Technicians:
  • Take ticket ownership promptly to show accountability
  • Add regular follow-ups to keep requesters informed
  • Use private tasks for internal coordination
  • Document solutions clearly for knowledge sharing
  • Link related tickets and assets for better tracking

Keyboard Shortcuts

ShortcutAction
Alt+TGo to main ticket view
Shift+PJump to processing tab
Alt+SGo to statistics tab
TQuick access to tickets (global shortcut)

Troubleshooting

Cannot create a ticket
  • Verify you have the appropriate permissions
  • Ensure required fields are filled in
  • Check entity access rights
Cannot update a ticket
  • Self-service users cannot update tickets with existing follow-ups or tasks
  • Closed tickets require special permissions to reopen
  • Verify you have rights to the ticket’s entity
SLA not appearing
  • Ensure SLA rules are configured for your entity
  • Check that the ticket category and priority match SLA criteria
  • Verify the ticket type (incident/request) matches SLA conditions

Build docs developers (and LLMs) love