Skip to content

Tickets reference

The factual list of fields, statuses, and settings of the Tickets module. For step-by-step actions, see Creating and handling tickets and Configuring tickets.

FieldRequiredDescription
SubjectyesA short statement of the request
DescriptionnoDetails
CategorynoA category from the directory; may define custom fields
TypenoSee the “Types” table
PrioritynoSee the “Priorities” table
RequesternoAn employee from the directory or the “Other” option
AssigneenoThe user handling the ticket
AssetsnoOne or more linked assets
Due DatenoThe deadline
SourcenoSee the “Sources” table

You can attach files to a ticket on the Attachments tab — see Files and photos.

The status set is configurable; the defaults are below.

StatusCode
Newnew
In Progressin_progress
On Holdon_hold
Resolvedresolved
Closedclosed
Cancelledcancelled

Incident · Service Request · Question · Problem.

Low · Medium · High · Critical.

Web · Email · Phone · API.

ViewContents
AllAll tickets
MineAssigned to the current user
UnassignedWithout an assignee
OverduePast the due date
ClosedIn the “Closed” status
ParameterDescription
First ResponseThe time to first response
ResolutionThe time to resolution
Status badgeTime remaining, a warning, or “SLA Breached”

The targets are set per priority and counted by the company’s business hours.

The Settings → Ticket Settings section: Categories · Routing · Statuses · Status reasons · Priorities · Types · SLA. Auto-assignment is configured on the Routing tab — a rule matches tickets by type, priority, and category and assigns them to a group or user (see Configuring tickets).

The Ticket Analytics page: Total Tickets · SLA Compliance · MTTR · Avg First Response. Plus breakdowns by status and priority and a trend over time.

Ticket permissions follow the tickets.* pattern: view, create, edit, delete, assign, analytics, and settings. They are assigned through the user’s role.