Incident Workflow

On this page

Default Workflow: This page describes the incident workflow of a new Alloy Navigator 2026.1 database created with the Default Workflow. An upgraded database need not have this content, and an administrator may have changed it. See Default Workflow Configuration.

In this configuration, there is no general status-change action; you change an incident's status with the named actions on this page. For where a ticket's actions are in the Web App and in the Mobile App, and how to run them, see Work on a Ticket.

Take an incident from Unassigned to Closed

  1. Assign the incident. To take it yourself, run Assign to me: you become the assignee, and the status becomes In Progress. The action sets Assigned, and the incident moves on at once, because an Assigned incident that its assignee saves moves to In Progress. To assign it to someone else or to a group, run Assign to..., choose the assignee group, the assignee, or both, and click Submit.
  2. Record your work with Log Work, which is offered only to the incident's assignee. It sets In Progress when the incident is Assigned. Saving an Assigned incident while you are its assignee also moves it to In Progress.
  3. Run Resolve Incident. The status becomes Resolved.
  4. Run Close Incident, choose a Closure Code, and click Submit. The status becomes Closed.

To reply to the requester along the way, run Notify Requester; see Reply to the requester. Resolve Incident stops when the requester of the incident, or of a child work order that it sets to Completed, has no valid primary e-mail address; see Find out why an action stops on an e-mail address. An incident that stays Resolved without changes is closed automatically after a set number of days; see Automatic status changes.

Other incident tasks

Put an incident on hold

Run Place On Hold, offered in Assigned, In Progress, and Approved. The status becomes On Hold. To continue, run Take Off Hold, which sets In Progress.

Reopen a closed incident

Run Reopen Incident. It sets In Progress, or Unassigned when the incident has a group but no assignee, and clears the resolution.

Mark a major incident or a duplicate, or make a request

  • Mark as Major Incident sets the type to Major Incident; the status stays.
  • Mark Duplicate closes the incident with the closure code Ticket Duplicated and relates it to the incident it duplicates.
  • Make Request closes the incident with the closure code Ticket Converted and creates a service request from it.

Request an approval

Create Approval is offered in Assigned and In Progress. Request Approval is offered in the same statuses while the incident has a pending approval stage and a pending approval request, and it sets Pending Approval. In Pending Approval, a pending approver of a pending approval stage votes with Approve Request or Reject Request; on a stage of the Sequential Approval type, only the first pending approver by rank is offered them. The approval outcome sets Approved or Rejected. See Approvals.

Escalate an incident

Run Escalate Incident, which is offered in every status except Closed and Rejected, to the Administrator (Full), Administrator (Workflow), Service Desk Manager, and Service Desk Technician roles. Its form, "Escalate this Incident", requires Escalate to and a Comment. Escalate to lists the active technicians, and you can choose several; it is pre-filled with the manager of the incident's service. The form also offers CC, which lists the same technicians, Time Spent, Publish to Self-Service Portal, which starts cleared, and attachments.

When you submit the form, the action:

  • e-mails the technicians in Escalate to, with the technicians in CC in copy;
  • marks the incident as escalated (see SLA metrics);
  • logs an activity in the Escalation category, with your comment as its details;
  • notifies the incident's collaborators who are technicians, while the workflow parameter Notify Collaborators on Events is on, as it is in the supplied configuration.

Escalating changes neither the status nor the assignment: the status, the assignee, and the assignee group stay as they are.

When you run the action and a person you chose has no primary e-mail address, the action stops with the message "<name>'s Primary E-mail does not exist. Please review as this process will result in an E-mail notification." When the address is not a valid e-mail address, the action stops with a message that names the person and says so. A stopped action saves nothing: the incident is not marked as escalated, no activity is logged, the collaborators are not notified, and no e-mail is sent.

Send a meeting request

Run Send Meeting Request, which is offered in every status except Closed, to the Administrator (Full), Administrator (Workflow), Service Desk Manager, and Service Desk Technician roles. Its form, "Send Meeting Request", requires a Time, a Location, chosen from the list of locations, and To, which is pre-filled with the incident's requester. It also offers a Comment, which is not required on an incident, CC, BCC, and attachments. To, CC, and BCC list every active person, not only technicians.

When you submit the form, the action:

  • sends one e-mail, the meeting request, to the people in To, CC, and BCC, with a calendar file built from the chosen time;
  • logs the activity "Meeting request was sent" in the Communication category, with the meeting time, the meeting place, and your comment as its details, and publishes it to the Self Service Portal;
  • notifies the incident's collaborators;
  • makes the people in CC who are not technicians collaborators of the incident, while the workflow parameter Convert CC'd Persons in E-mail to Collaborators is on, as it is in the supplied configuration. A person in BCC does not become a collaborator. Each new collaborator is e-mailed "Added as a Collaborator (Incident):" followed by the incident's summary, while the workflow parameter Notify Collaborators on Creation is on, as it is in the supplied configuration.

The status does not change. The action stops when a person in To, CC, or BCC, or an active collaborator of the incident, has no valid primary e-mail address; see Find out why an action stops on an e-mail address.

Start a TeamViewer session

Incidents carry two actions for a TeamViewer remote session with the requester:

  • TeamViewer Invite e-mails the incident's requester an invitation that carries a session code and a join button.
  • TeamViewer Connect opens the session once the requester has authorized it.

To start a session:

  1. Open the incident.
  2. Run TeamViewer Invite. The requester receives the invitation by e-mail.
  3. Once the requester has authorized the session, run TeamViewer Connect to open it.

An incident offers the two actions only while the TeamViewer integration is enabled and its script token and group number are filled in; on a system where the integration is not configured, they are not offered. How to set up the integration is described in TeamViewer.

Run TeamViewer Invite first. TeamViewer Connect is not hidden before an invitation is sent: if you run it while no session is stored for the incident, a workflow message tells you to run TeamViewer Invite first, and the action stops.

Use a consumable

Run Use Consumable, which is offered in Assigned, In Progress, and Approved while the incident's related CI is a computer or a hardware item, to the Administrator (Full), Administrator (Workflow), Service Desk Manager, and Service Desk Technician roles. Its form, "Use a Consumable", requires a Consumable, chosen from the active consumables, a Quantity Used, which starts at 1, and a Reason, chosen from the active stock movement reasons. Related CI shows the incident's related CI and cannot be changed. The form also offers Comment and Time Spent. It asks for no date: the stock movement is dated with the current date and time.

When you submit the form, the action takes the quantity used off the consumable, records a stock movement from the consumable's stock room to the CI's asset, and sets the consumable to Depleted when the quantity used is all that was left. It logs the use on the incident, on the CI, and on the consumable, and relates the incident and the CI to the consumable: the consumable lists them under Used in, and they list the consumable under Used. The incident's status does not change.

The consumable's own checks can refuse the action with "There are no consumables currently available for use." when the consumable's quantity is empty or 0 or the consumable is Depleted, or with "You are attempting to use more consumables (<quantity used>) than are currently available (<quantity left>)." For consumables and stock movements, see Stock and Consumables.

Create a problem from an incident

Run Create Problem, which is offered in Assigned, In Progress, On Hold, and Approved while the incident has no related problem. It is granted to the Administrator (Full), Administrator (Workflow), Problem Manager, Problem Technician, and Service Desk Manager roles, but not to the Service Desk Technician role.

Its form, "Create a Problem", requires a summary, a description, a type, and a requester. The summary and the description are pre-filled with the incident's, and the requester with you; only a technician can be the requester. The project and the related CI are pre-filled with the incident's, and the service with General Problem. You can also set the category, the assignee group, the assignee, the urgency, and the impact, and add attachments; once a group is set, the assignee lists only the group's members.

When you submit the form, the action:

  • creates a problem from the form's values, in the incident's workspace, and gives it the form's attachments; the problem takes the organization of its requester;
  • runs auto-assignment on the new problem, which starts as Unassigned: it stays Unassigned when only a group is set, and becomes Assigned, with an e-mail to the assignee, when an assignee is set;
  • sets the incident's related problem to the new problem;
  • logs "Created Related Problem" on the incident.

In the Web App, the new problem opens when the action completes. The incident's status does not change, and because the incident now has a related problem, Create Problem is no longer offered on it. When the problem is resolved with Resolve related Incidents selected, the incident becomes Resolved unless it is already Resolved or Closed; see Automatic status changes and Problem Workflow.

Create a change request from an incident

Run Create Change Request, which is offered in Assigned, In Progress, On Hold, and Approved while the incident has no change request. It is granted only to the Administrator (Full), Administrator (Workflow), Change Request Manager, and Change Request Technician roles, and to no Service Desk role.

Its form, "Create a Change Request", has the fields of the "Create a Problem" form (see Create a problem from an incident), with three differences: the type lists the change request types, the service is pre-filled with General Change Request, and the form also offers a scheduled start date and a scheduled end date, both optional. The assignee group and the assignee are pre-filled with the incident's.

When you submit the form, the action:

  • creates a change request from the form's values, including the scheduled dates, in the incident's workspace, and gives it the form's attachments; the change request takes the organization of its requester;
  • runs auto-assignment on the new change request: it becomes Assigned, with an e-mail to the assignee and its start date set, when the form names an assignee, and it stays in Draft otherwise;
  • sets the incident's change request to the new change request;
  • logs "Created Related Change Request" on the incident.

In the Web App, the new change request opens when the action completes. The incident's status does not change, and Create Change Request is no longer offered on it. For the change request's own workflow, see Change Request Workflow.

Create a knowledge base article from an incident

Run Create Quick Article, which is offered in Assigned, In Progress, On Hold, Approved, Pending Approval, Rejected, and Resolved. It is granted to the Administrator (Full), Administrator (Workflow), Knowledge Base Contributor, Knowledge Base Manager, Service Desk Manager, and Service Desk Technician roles.

Its form, "Create a Knowledge Base Article", requires a type, a title, the content, and a resolution. The title is pre-filled with the incident's summary, the content with the incident's description, and the resolution with the incident's resolution. You can also add attachments.

When you submit the form, the action:

  • creates a knowledge base article related to the incident, in the incident's workspace, and gives it the form's attachments;
  • logs "Created Related Knowledge Base Article" on the incident.

The new article is at the status Draft, is private, and has version 1.0. It has no owner and no author. Its content holds the content and the resolution from the form under the headings OVERVIEW and SOLUTION, followed by the heading REFERENCE with the text "No References Currently Exist." The article lists the incident under Solution for, and the incident lists the article under Solved by. In the Web App, the article opens when the action completes. The incident's status does not change. The article stays private until Make Public is run on it or the last approval stage created for it is approved; see Knowledge Base Article Workflow.

Create a work order from an incident

Run Create Work Order, which is offered in Assigned, In Progress, On Hold, and Approved, to the Administrator (Full), Administrator (Workflow), Service Desk Manager, and Service Desk Technician roles.

Its form, "Create a Work Order", requires a summary and a description, which are pre-filled with the incident's, a type, and a requester, who must be a technician and is pre-filled with you. The project and the related CI are pre-filled with the incident's, and the service with General Work Order. You can also set the category, the assignee group, the assignee, the urgency, the impact, and the scheduled start and end dates, and add attachments; the assignee can only be a member of the group chosen on the form.

When you submit the form, the action:

  • creates a work order whose parent is the incident, in the incident's workspace, and gives it the form's attachments; the work order takes the organization of its requester;
  • runs auto-assignment on the new work order, which starts as Unassigned: it stays Unassigned when only a group is set, and becomes Assigned, with an e-mail to the assignee, when an assignee is set;
  • logs "Created Related Work Order" on the incident.

In the Web App, the new work order opens when the action completes. The incident's status does not change. For the work order's own workflow, see Work Order Workflow.

Statuses and lifecycle stages

An incident uses nine statuses: Unassigned, Assigned, In Progress, On Hold, Resolved, and Closed, and, for approvals, Pending Approval, Approved, and Rejected.

A new incident is created as Unassigned. Unless it is created through the API, auto-assignment then runs on it, and the incident becomes Assigned when its form names an assignee or auto-assignment picks one. When the incident has neither an assignee group nor an assignee, it gets the support group of its service, while the workflow parameter Service Support Group Assignment is on, as it is in the supplied configuration. When it has no assignee, auto-assignment picks one among the active members of the group whose work calendar shows them available for the next 15 minutes: with the workflow parameter Assignee Load Balancing Method set to Least amount of tickets, as it is for incidents in the supplied configuration, it picks the member with the fewest incidents at Unassigned, Assigned, or In Progress. When no member is available, the incident stays Unassigned with the group; see Automatic status changes.

In the Web App, the progress bar at the top of an incident's full form shows five lifecycle stages (see Follow the ticket's progress):

Stage Statuses
Submission Unassigned, Assigned
Approval Pending Approval, Rejected
Planning Approved, On Hold
Resolving In Progress
Close Resolved, Closed

Action reference

Action Offered in What it does
Assign to me Unassigned, Assigned, In Progress, Approved, Resolved, when the incident has no assignee or another assignee Makes you the assignee and your top-ranked group the assignee group, sets the status to Assigned, sets the start date if it is empty, logs "Current User assigned to self", and notifies the collaborators. The incident then moves on to In Progress, as an Assigned incident does when its assignee saves it.
Assign to... Unassigned, Assigned, In Progress, Approved, Resolved Opens the form "Assign this Incident" with Assignee Group, Assignee, Comment, and Time Spent, none of them required. It logs "Record was assigned" and notifies the collaborators. The status becomes Unassigned when only a group is set and Assigned when a new assignee is set; otherwise it stays. On a Resolved incident, it also clears the resolution.
Place On Hold Assigned, In Progress, Approved Sets On Hold and logs "Marked as 'On Hold'".
Take Off Hold On Hold Sets In Progress and logs "Taken off 'On Hold'".
Mark as Major Incident Assigned, In Progress, Approved, while the type is not Major Incident Sets the type to Major Incident; the status stays.
Resolve Incident Assigned, In Progress, On Hold, Approved, Rejected Sets Resolved, and sets the completed date if it is empty.
Log Work Every status except Closed, and only for the incident's assignee Sets In Progress when the incident is Assigned; otherwise the status stays.
Add Comment Every status except Closed, when the incident has no assignee or another assignee The status stays. It is not offered to the incident's assignee.
Close Incident Resolved Sets Closed, logs "Marked as 'Closed'", and sends notifications. The form requires a Closure Code.
Reopen Incident Closed Sets In Progress, or Unassigned when the incident has a group but no assignee, and clears the resolution.
Mark Duplicate Every status except Closed Closes the incident with the closure code Ticket Duplicated and relates it to the incident it duplicates.
Make Request Assigned, In Progress Closes the incident with the closure code Ticket Converted and creates a service request from it.
Escalate Incident Every status except Closed and Rejected, for the Administrator (Full), Administrator (Workflow), Service Desk Manager, and Service Desk Technician roles E-mails the technicians chosen in the form, marks the incident as escalated, and logs an activity. The status, the assignee, and the assignee group stay.
Send Meeting Request Every status except Closed, for the Administrator (Full), Administrator (Workflow), Service Desk Manager, and Service Desk Technician roles E-mails a meeting request to the people in To, CC, and BCC, with a calendar file built from the chosen time, logs the activity "Meeting request was sent", and publishes it to the Self Service Portal. The status stays.
Use Consumable Assigned, In Progress, Approved, while the incident's related CI is a computer or a hardware item, for the Administrator (Full), Administrator (Workflow), Service Desk Manager, and Service Desk Technician roles Takes the quantity used off a consumable and relates the incident and its related CI to the consumable. The status stays.
Create Problem Assigned, In Progress, On Hold, Approved, while the incident has no related problem, for the Administrator (Full), Administrator (Workflow), Problem Manager, Problem Technician, and Service Desk Manager roles Creates a problem from the form and sets it as the incident's related problem. The status stays.
Create Change Request Assigned, In Progress, On Hold, Approved, while the incident has no change request, for the Administrator (Full), Administrator (Workflow), Change Request Manager, and Change Request Technician roles Creates a change request from the form, Assigned when the form names an assignee and in Draft otherwise, and sets it as the incident's change request. The status stays.
Create Quick Article Assigned, In Progress, On Hold, Approved, Pending Approval, Rejected, Resolved, for the Administrator (Full), Administrator (Workflow), Knowledge Base Contributor, Knowledge Base Manager, Service Desk Manager, and Service Desk Technician roles Creates a private knowledge base article at the status Draft from the form, related to the incident. The status stays.
Create Work Order Assigned, In Progress, On Hold, Approved, for the Administrator (Full), Administrator (Workflow), Service Desk Manager, and Service Desk Technician roles Creates a work order whose parent is the incident. The status stays.

The approval actions are part of the same list; see Request an approval. For the Log Work form, the automatic timer, Notify Requester, and Notify Assignee, see Work on a Ticket.

Mark Duplicate, Approve Request, Reject Request, Add Comment, and Notify Assignee are offered to every role of the supplied configuration except the Administrator (Log Management), Administrator (Security), Administrator (Services), Administrator (Views/Dashboards), Report Designer, Report Viewer, and Viewer roles.

The close action changes only the incident itself: its work orders and approvals stay as they are, and no warning appears when the incident still has open work orders.

Actions in the Web App

In the Web App, an incident's full form puts these actions in the Communication and Relationships sections of its Action Bar, in this order:

  • Communication: Add Comment, Log Work, Notify Assignee, Notify Requester, Send Meeting Request, Escalate Incident, Automatic Timer On, and Automatic Timer Off.
  • Relationships: Use Consumable, Create Problem, Create Work Order, Create Change Request, and Create Quick Article.

Escalate Incident, Send Meeting Request, Use Consumable, Create Problem, Create Change Request, and Create Quick Article are not on the form's toolbar. In an incident list, they can also be run on several selected incidents; see Run an action on several records. Create Work Order is not on the form's toolbar either.

Collaborators, Copy Incident, Follow, Make Request, Mark Duplicate, and Unfollow, listed here in alphabetical order, are only on the form's toolbar, not on the Action Bar. For the Action Bar and the toolbar, see Actions in the Web App.

Automatic status changes

  • When an Assigned incident is saved while you are its assignee, it moves to In Progress.
  • When an incident is resolved, its child work orders that are not Closed are set to Completed.
  • When the last of an incident's work orders that is not Closed is completed, the incident becomes Resolved. This rule and the one above are each controlled by a workflow parameter of their own, and both are turned on in the supplied configuration.
  • When a problem is resolved with Resolve related Incidents selected, the incidents whose related problem it is, and that are neither Resolved nor Closed, become Resolved. See Problem Workflow.
  • While the workflow parameter Auto Assignment After Hours Handling is set to Auto-Assign Next Business Day and Assignee Load Balancing Method is not set to Disable load balancing, as in the supplied configuration, an incident that is Unassigned is checked every 15 minutes during the hours of the Default Work Calendar: the activity "Auto-Assign Next Business Day" is logged, the incident's service is set to Technical Support, whatever service it had, the incident keeps its assignee group, and auto-assignment runs again. The incident becomes Assigned when that sets an assignee; otherwise it stays Unassigned. This check also picks up an incident that was created when no member of its group was available, or that was reopened without an assignee.
  • An incident that stays Resolved without changes for the number of days in its workflow parameter is closed automatically. The day count is set to 14 in the supplied configuration, and a value of 0 turns the automatic closing off. The activity logged gives the number of days, for example "Automatically Closed after 14 day(s)".