Tickets

On this page

A ticket is a record of one of five classes: Incident, Problem, Change Request, Service Request, or Work Order. The five share a common set of fields for identification, requester and assignee, classification, scheduling, and effort. The All Tickets and My Tickets lists combine these five classes. A Project Task is not a ticket.

Technicians work with tickets in the Web App. How a ticket moves from status to status is set by the workflow configuration; see Workflow Overview.

What separates one ticket class from another

The ticket classes are related to one another:

  • A Problem is the underlying cause of one or more Incidents. An Incident can be linked to the Problem it was attributed to, and the Problem lists those Incidents on its Related Incidents tab.
  • A Change Request is a formal proposal to make a change.
  • A Work Order is a piece of work to be carried out. It can be placed below a ticket of any class, or it can stand on its own, for example to prepare a workstation for a new employee. We recommend a Work Order below a Change Request to implement the change once it is approved, and below an Incident or a Problem to fix it.

The five classes share most of their fields. The table lists what is specific to each class.

Class What it has that not every ticket class has
Incident A resolution narrative kept separate from the ticket's notes; a link to the Problem the Incident was attributed to; a link to the Change Request raised from it; a Metrics panel that no other class has.
Problem A link to the Change Request raised from it; a Related Incidents tab.
Change Request A planned start and end window.
Service Request A link to the Service Catalog Item it was raised from; a planned start and end window.
Work Order A resolution narrative kept separate from the ticket's notes; a parent ticket (see Hierarchy); a planned start and end window.

Incident and Problem have no planned window.

Incidents and Service Requests carry a setting that decides whether the requester may rate the outcome. An Incident, a Service Request, or a Work Order keeps at most one rating, its requester's.

The one status the platform owns

Each ticket class has exactly one status that the platform itself defines: Closed. Every other status comes from the workflow configuration.

Closed behaves differently from every other status:

  • The Closed status cannot be deleted.
  • A ticket counts as active in every status except Closed.
  • A reopen action is offered only while the ticket is Closed, whatever statuses the action was set up with.
  • A workflow action set up without a list of statuses is offered in every status except Closed.

Identity, hierarchy, and participants

Identity

Every ticket has a ticket number. The format of the number is set by the workflow configuration.

Hierarchy

Only a Work Order can have a parent, and its parent can be a ticket of any of the five classes, including another Work Order. A Work Order does not need a parent. Alloy Navigator does not warn you about open Work Orders below a ticket when the ticket is closed.

A ticket's time spent is the total time of its own activities. Its cumulative time spent adds the activity time of every Work Order below it, at any depth. Both totals are recalculated when an activity's time is entered or changed and when an activity is deleted; moving a Work Order to another parent recalculates the cumulative time spent.

Participants

Besides its requester, assignee, and assignee group, a ticket can have collaborators: people related to the ticket by the collaborators relationship type. That relationship type comes from the workflow configuration. In a new 2026.1 database created with the Default Workflow, it is Collaborating / Collaborators. An upgraded database need not have it, and an administrator may have changed it.

In the Web App

Ticket lists

The Service Desk menu holds one list per ticket class, Incidents, Service Requests, Problems, Change Requests, and Work Orders, and the combined All Tickets list, beside Approval Requests, Knowledge Base, and Announcements. You see an entry only when you may view its class. The menu can take up to five minutes to reflect a change to your permissions. Approval stages have no menu entry of their own; they are offered in advanced search, including when you search for a related object.

My Tickets, under My Work, lists the open tickets assigned to you or to a group you belong to. Closed tickets are never listed there, whatever filter or view you apply. A ticket waiting for your approval appears only when it is also assigned to you or your group. You see My Tickets only when you may view the class of the All Tickets list.

In the Incidents and Service Requests lists, a requester's rating and rating comment are shown to technicians who may view all ratings, and to technicians who may view their own ratings on a ticket whose assignee they are.

All Tickets

All Tickets is a single list that combines the five ticket classes. It has no New button and no Batch Update entry in the Actions menu. It keeps the preview pane: the Options button offers Show on the right, Show on the bottom, and Hide.

Selecting rows of more than one ticket class has two effects:

  • The Actions flyout shows No Actions.
  • Delete is disabled.

For a selection within one class, Delete follows your delete permission for the class of the last row you selected. Without that permission, Delete is disabled and shows Permission denied.

The confirmation depends on where you choose Delete, not on how many rows are selected. From a row's own menu, you are asked "Are you sure you want to delete this item?". From the toolbar's Actions menu, you are asked "Warning! You are about to delete n selected records.", with the number of selected rows, even when only one row is selected. On confirmation, the rows are deleted and the list refreshes.

An administrator chooses which fields the All Tickets list can show in the Admin Center; see User-Defined Fields.

The ticket form

All five classes share the same tabs: a General tab, a Relationships tab, and tabs for approvals, Work Orders, custom data, notes, history, and attachments. The custom data tab is left out when the class has no custom fields placed on a tab of their own, and the General tab's custom data area is left out when no custom fields are placed on the General tab. A resolution tab appears only on Incident and Work Order, and a Related Incidents tab only on Problem. The Work Orders tab lists the ticket's Work Orders. Activity is a panel at the end of the General tab, not a tab of its own.

The Related Incidents tab of a Problem lists the Incidents whose related Problem is that Problem. Opening a row there opens the Incident in the current window, or in a new tab when your setting to open objects in a new window is on.

The Relationships tab lists the objects related to the ticket, grouped by relationship type. Some of those relationships are held by a field of the ticket itself: the related configuration item of any ticket, the related Problem and the Change Request of an Incident, and the Change Request of a Problem. Such a relationship leaves the tab when the field that holds it is cleared or pointed to another record, and its row's check box on the tab is disabled.

The panels of the General tab differ by class:

  • A Service Request, a Problem, and a Change Request have the Details, Categorization, Requester Information, Assignment, Prioritization, and Performance panels and the custom data area, followed by Description and Activity.
  • On an Incident, the Details panel holds the requester and assignment fields together with the related Problem and the Change Request, and a Metrics panel has fields for whether the Incident was escalated, resolved the first time, overdue for response or resolution, or reopened, and for its response and resolution times. Alloy Navigator itself does not fill these fields; the workflow configuration does, and they stay empty when it does not.
  • A Work Order has no Performance panel; its dates, time spent, and closure code are in its Prioritization panel.
  • The Incident, Service Request, and Work Order forms have a Feedback panel that shows the requester's rating as read-only stars, at half-star precision, and their comment, which cannot be edited. When the form carries the setting that decides whether the requester may rate the outcome, the panel shows it too. The panel is left out when no feedback record exists for the ticket's current assignee.

The progress bar at the top of a ticket shows the lifecycle stages of its class in order and highlights the stage its current status belongs to. The stage changes only when the status changes. A status that belongs to no stage highlights none. A class with no lifecycle stages shows no progress bar.

The browser tab of an open ticket shows its ticket number and summary.