Problem Workflow

On this page

Default Workflow: This page describes the problem 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 a problem's status with the named actions on this page. For where a ticket's actions are and how to run them, see Work on a Ticket.

Take a problem from Unassigned to Closed

  1. Assign the problem. To take it yourself, run Assign to me: you become the assignee, and the status becomes In Progress. The action sets Assigned, and the problem moves on at once, with the activity "Assignee has begun work", because an Assigned problem 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 problem's assignee. It sets In Progress when the problem is Assigned. Saving an Assigned problem while you are its assignee also moves it to In Progress.
  3. Run Resolve Problem. The status becomes Resolved. To resolve at the same time the incidents whose related problem is this problem, select Resolve related Incidents on the form.
  4. Run Close Problem, choose a Closure Code, and click Submit. The status becomes Closed.

A problem that stays Resolved without changes is closed automatically after a set number of days; see Automatic status changes. Resolve Problem stops when the requester of the problem, 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.

Other problem tasks

Mark a known issue

Run Mark Known Issue, offered in Assigned and In Progress. The status becomes Known Issue. Resolve Problem is offered on a problem at Known Issue.

Put a problem on hold

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

Reopen a closed problem

Run Reopen Problem. It sets In Progress, or Unassigned when the problem has a group but no assignee, and clears the completed date and the closure code.

Mark a duplicate

Mark Duplicate closes the problem with the closure code Ticket Duplicated and relates it to the problem it duplicates. In the Web App, it is on the toolbar of the problem's full form, not on the Action Bar.

Create a change request from the problem

Run Create Change Request. It is offered in Assigned, In Progress, Known Issue, and On Hold while the problem's change request field is empty. It is granted to the Administrator (Full), Administrator (Workflow), Change Request Manager, Change Request Technician, and Problem Manager roles, and not to the Problem Technician role. In the Web App, it is in the Relationships section of the Action Bar.

The form "Create a Change Request" requires a Summary and a Description, which are pre-filled with the problem's, a Type (one of the change request types), and a Requester, which starts empty and can only be a technician. Its Organization field, before the Requester, narrows the requester list to the technicians of the chosen organization. The project and the related CI are pre-filled with the problem's, and the service with General Change Request.

The action logs "Created Related Change Request" on the problem and creates a change request from the form, in the problem's workspace, and writes it into the problem's change request field. The change request becomes Assigned, with an e-mail to the assignee and its start date set, when the form names an assignee, and stays in Draft otherwise; the form's assignee group and assignee start empty. It takes the organization of its requester, which is the organization chosen on the form when you pick the requester from the narrowed list. It gets the form's attachments and opens when the action completes. The problem's status does not change. For the change request's own workflow, see Change Request Workflow.

Create a knowledge base article from the problem

Run Create Quick Article. It is offered in Assigned, In Progress, Known Issue, On Hold, and Resolved, and it is granted to the Administrator (Full), Administrator (Workflow), Knowledge Base Contributor, Knowledge Base Manager, Service Desk Manager, Problem Manager, and Problem Technician roles. In the Web App, it is in the Relationships section of the Action Bar.

The form "Create a Knowledge Base Article" requires a Type, a Title, and the Content; the title and the content are pre-filled with the problem's summary and description. The Resolution is optional and starts empty.

The action logs "Created Related Knowledge Base Article" on the problem and creates a knowledge base article related to the problem, in the problem's workspace. The article starts at Draft, with the version 1.0 and its public flag cleared, so it is private. Its content is built from the form: the heading "OVERVIEW" with the Content, the heading "SOLUTION" with the Resolution, and the heading "REFERENCE" with "No References Currently Exist." The article has no owner and no author. It lists the problem under Solution for, and the problem lists the article under Solved by. The article gets the form's attachments and opens when the action completes. The problem'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 the problem

Run Create Work Order. It is offered in Assigned, In Progress, Known Issue, and On Hold, and it is granted to the Administrator (Full), Administrator (Workflow), Problem Manager, and Problem Technician roles. In the Web App, it is in the Relationships section of the Action Bar.

The form "Create a Work Order" requires a summary and a description, which are pre-filled with the problem's, a type, and a requester. The requester starts empty and can only be a technician; the form's organization field, which starts empty, narrows the requester list. The project and the related CI are pre-filled with the problem'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.

The action logs "Created Related Work Order" on the problem and creates a work order whose parent is the problem, in the problem's workspace, with the form's attachments. The work order takes the organization of its requester, which is the organization chosen on the form when you pick the requester from the narrowed list. Auto-assignment runs 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. The new work order opens when the action completes. The problem's status does not change. For the work order's own workflow, see Work Order Workflow.

Statuses and lifecycle stages

A problem uses seven statuses: Unassigned, Assigned, In Progress, On Hold, Known Issue, Resolved, and Closed. It has no approval statuses and no approval actions.

A new problem is created as Unassigned. Unless it is created through the API, auto-assignment then runs on it. The form "Create a Problem" has an Assignee Group and an Assignee, both optional, and the assignee can only be a member of the chosen group. A problem whose form names an assignee starts as Assigned: the assignee is e-mailed, and the start date is set. A problem with only a group starts as Unassigned with that group. A problem with neither gets the support group of its service, while the workflow parameter Service Support Group Assignment is on, as it is in the supplied configuration, and starts as Unassigned. Auto-assignment picks no assignee for a problem: the workflow parameter Assignee Load Balancing Method is set to Disable Load Balancing for problems in the supplied configuration.

A problem has four lifecycle stages and no Approval stage. In the Web App, the progress bar at the top of a problem's full form shows them (see Follow the ticket's progress):

Stage Statuses
Submission Unassigned, Assigned
Planning On Hold
Resolving In Progress, Known Issue
Close Resolved, Closed

Action reference

Action Offered in What it does
Assign to me Every status except Closed, when the problem has no assignee or another assignee Makes you the assignee and your top-ranked group the assignee group, sets the status to Assigned, and sets the start date if it is empty. The problem then moves on to In Progress, as an Assigned problem does when its assignee saves it.
Assign to... Every status except Closed Opens the form "Assign this Problem" with Assignee Group, Assignee, Comment, and Time Spent, none of them required. The status becomes Unassigned when only a group is set and Assigned when a new assignee is set; otherwise it stays.
Place On Hold Assigned, In Progress Sets On Hold.
Take Off Hold On Hold Sets In Progress and logs "Take off 'On Hold'".
Mark Known Issue Assigned, In Progress Sets Known Issue and logs "Marked as 'Known Issue'".
Resolve Problem Assigned, In Progress, Known Issue, On Hold Sets Resolved, and sets the completed date if it is empty. With Resolve related Incidents selected, it also sets Resolved, with "Resolved by related Problem", on every incident whose related problem is this problem and that is not already Resolved or Closed.
Log Work Every status except Closed, and only for the problem's assignee Sets In Progress when the problem is Assigned; otherwise the status stays.
Add Comment Every status except Closed, when the problem has no assignee or another assignee The status stays. It is not offered to the problem's assignee.
Mark Duplicate Every status except Closed Closes the problem with the closure code Ticket Duplicated and relates it to the problem it duplicates.
Close Problem Resolved Sets Closed, logs "Marked as 'Closed'", and sends notifications. The form requires a Closure Code.
Reopen Problem Closed Sets In Progress, or Unassigned when the problem has a group but no assignee, and clears the completed date and the closure code.
Create Change Request Assigned, In Progress, Known Issue, On Hold, while the problem's change request field is empty; only for the Administrator (Full), Administrator (Workflow), Change Request Manager, Change Request Technician, and Problem Manager roles Creates a change request, Assigned when the form names an assignee and in Draft otherwise, and writes it into the problem's change request field; the status stays. See Create a change request from the problem.
Create Quick Article Assigned, In Progress, Known Issue, On Hold, Resolved; only for the Administrator (Full), Administrator (Workflow), Knowledge Base Contributor, Knowledge Base Manager, Service Desk Manager, Problem Manager, and Problem Technician roles Creates a private knowledge base article at Draft, related to the problem; the status stays. See Create a knowledge base article from the problem.
Create Work Order Assigned, In Progress, Known Issue, On Hold; only for the Administrator (Full), Administrator (Workflow), Problem Manager, and Problem Technician roles Creates a work order whose parent is the problem; the status stays. See Create a work order from the problem.

For the Log Work form, the automatic timer, Notify Requester, and Notify Assignee, see Work on a Ticket.

Mark Duplicate, 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 problem itself: its work orders and approvals stay as they are, and no warning appears when the problem still has open work orders.

Actions in the Web App

In the Web App, on a problem's full form, the Relationships section of the Action Bar holds, in this order, Create Work Order, Create Change Request, and Create Quick Article, and none of the three is on the toolbar. Collaborators, Copy Problem, Follow, Mark Duplicate, and Unfollow, listed here in alphabetical order, are on the toolbar only, not on the Action Bar. For the Action Bar and the toolbar, see Find a ticket's actions.

Automatic status changes

  • When an Assigned problem is saved while you are its assignee, it moves to In Progress.
  • When a problem is resolved, its child work orders that are not Closed are set to Completed.
  • When the last of a problem's work orders that is not Closed is completed, the problem 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.
  • A problem 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)", and a problem closed this way gets the closure code Resolution Assumed.