Change Request Workflow

On this page

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

Take a change request from Draft to Closed

Unless a step names fewer roles, the actions in these steps are offered to the Administrator (Full), Administrator (Workflow), Change Request Manager, and Change Request Technician roles.

  1. Assign the change request with Assign to me or Assign to...; both are offered in every status except On Hold, Pending Approval, and Closed. To take it yourself, run Assign to me, which is offered while you are not its assignee: you become the assignee, and the status becomes Assigned. Assign to... is offered only to the Administrator (Full), Administrator (Workflow), and Change Request Manager roles; in its form, choose the assignee group, the assignee, or both, and click Submit. The status becomes Assigned when you set a new assignee, and Draft when the change request is left with a group but no assignee; otherwise it stays.
  2. Run Schedule Work, enter the scheduled start date and the scheduled end date, and click Submit. Schedule Work is offered while the scheduled start date or the scheduled end date is empty, in every status except On Hold, Pending Approval, Completed, and Closed. The start date must be after the change request's submit date and before the end date, and the end date must be before its due date. The status stays.
  3. Run Implement Change, which is offered in Assigned, In Progress, Approved, Rejected, Tested, and Failed. It is not offered in Draft: if the change request is still Draft, first give it an assignee in step 1, which sets Assigned. On a change request of the type Emergency, Standard, or Unspecified, its form "Implement Change" has the fields Comment and Time Spent, neither of them required; on one of the type Minor, its form "Add a Comment" requires a Comment. Click Submit. The status becomes Implemented.
  4. On a change request of the type Emergency, Standard, or Unspecified, run Testing Completed, which is offered in Assigned, In Progress, and Implemented. In its form "Document Testing Results", choose Testing Passed or Testing Failed in Testing Results, and click Submit. Testing Passed sets Tested, and Testing Failed sets Failed; if you choose neither, the status stays. From Tested or Failed, you can run Implement Change again or go on to complete the change request. A change request of the type Minor skips this step: Testing Completed is not offered on it.
  5. Run Complete Request, fill in the "Add a Comment" form, and click Submit. On a change request of the type Emergency, Standard, or Unspecified, Complete Request is offered in Assigned, In Progress, On Hold, Approved, Rejected, Tested, Failed, and Implemented; on one of the type Minor, only in Assigned, In Progress, On Hold, and Implemented. The status becomes Completed, and the completed date is set if it is empty.
  6. Run Close Request, choose a Closure Code, and click Submit. Close Request is offered in Completed and only to the Administrator (Full), Administrator (Workflow), and Change Request Manager roles. The status becomes Closed.

To have the change approved, run Create Approval and then Request Approval, which sets Pending Approval; see Request an approval.

A change request that stays Completed without changes is closed automatically after a set number of days; see Automatic status changes. Complete Request stops when the requester of the change request, 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 change request tasks

Request an approval

Create Approval is offered in Draft, Assigned, and In Progress, and creates an approval stage. Request Approval is offered in Draft, Assigned, In Progress, Approved, Rejected, Tested, Failed, and Implemented while the change request 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. None of the actions of Take a change request from Draft to Closed is offered in Pending Approval. When the approval stage created last for the change request is approved or rejected, the change request becomes Approved or Rejected.

Cancel Approvals is offered in Draft, Assigned, In Progress, and Pending Approval while an approval stage is Pending or Pending Approval, and only to the Administrator (Full), Administrator (Workflow), and Approval Manager roles. It sets the Pending and Pending Approval approval stages and their pending approval requests to Not Required, and sets the change request to In Progress.

For how approvals work, see Approvals.

Put a change request on hold

Run Place On Hold, offered in Draft, Assigned, In Progress, Approved, Rejected, Tested, Failed, and Implemented. The status becomes On Hold. While it is on hold, the change request offers Complete Request, but not Implement Change or Testing Completed. To continue, run Take Off Hold: the status becomes In Progress, whatever it was before the hold. Both actions open the form "Provide a Reason", whose Comment and Time Spent are not required.

Reopen a closed change request

Run Reopen Request, which is offered on a Closed change request. Its form "Reopen Change Request" is pre-filled with the change request's assignee group and assignee, which you can change, and has the fields Comment and Time Spent; the assignee is limited to the members of the chosen group. Click Submit. The status becomes In Progress, or Draft when the change request has a group but no assignee, or Assigned, with an e-mail to the assignee, when you change the assignee. The completed date and the closure code are cleared.

Mark a duplicate

Run Mark Duplicate, which is offered in every status except Closed. In the Web App, it is on the form's toolbar, not on the Action Bar. In the "Mark Request as Duplicate" form, choose in Duplicate of, which is required, the change request that this one duplicates; the change request itself is not offered. The form also has Comment and Time Spent. Click Submit.

The action closes the change request with the closure code Ticket Duplicated, notifies its followers, and logs "Marked duplicate of <ticket>" on it, with your comment as the details. It relates the two change requests: this one lists the other under Duplicate of, and the other lists this one under Duplicated by. It also sets the start date, when the change request has an assignee, and the actual response date and the completed date, each only if it is empty. On the other change request, it logs an activity that begins "Duplicate ticket related", with your comment and this change request's description in its details, and notifies that change request's assigned party.

Create a work order from a change request

Run Create Work Order, which is offered in Draft, Assigned, In Progress, Approved, Rejected, Tested, Failed, and Implemented, to the Administrator (Full), Administrator (Workflow), Change Request Manager, and Change Request Technician roles. In the Web App, it is in the Relationships section of the Action Bar.

Its form, "Create Work Order", requires a summary and a description, which are pre-filled with the change request's, a type, a requester, a service, an urgency, and an impact. The service is pre-filled with General Work Order, the organization with the change request's, and the requester with you; the requester can be any person, and the requester list is filtered by the change request's own organization, not by the organization on the form; it is not filtered when the change request has no organization. You can also set the category, the project, the assignee group, the assignee, the scheduled start and end dates, and the related CI, and add attachments. The assignee can only be a member of the change request's own assignee group.

When you submit the form, the action logs "Created Related Work Order" on the change request and creates a work order whose parent is the change request, in the change request's workspace, with the form's attachments. The work order takes the organization of its requester, not the organization shown on the form; when the requester has no organization, the work order has none. The new work order starts as Unassigned; auto-assignment then runs on it, and it becomes Assigned, with an e-mail to the assignee, when an assignee is set. In the Web App, the new work order opens when the action completes. The change request's status does not change. For the work order's own workflow, see Work Order Workflow.

Create a knowledge base article from a change request

Run Create Quick Article, which is offered in Assigned, In Progress, On Hold, Approved, Rejected, Tested, Failed, Implemented, and Completed, to the Administrator (Full), Administrator (Workflow), Change Request Manager, Change Request Technician, Knowledge Base Contributor, and Knowledge Base Manager roles. In the Web App, it is in the Relationships section of the Action Bar.

Its form, "Create a Knowledge Base Article", requires a type, a title, and the content; the title and the content are pre-filled with the change request's summary and description. The resolution is optional and starts empty.

The action logs "Created Related Knowledge Base Article" on the change request and creates a knowledge base article related to it. The article starts at Draft, with version 1.0 and its public flag cleared, so it is private. Its content holds the form's content under the heading OVERVIEW and the resolution under SOLUTION, followed by the heading REFERENCE with "No References Currently Exist." In the Web App, the article opens when the action completes. The change request's status does not change. For the article's own workflow, including how it is made public, see Knowledge Base Article Workflow.

Statuses and lifecycle stages

A change request uses twelve statuses: Draft, Assigned, In Progress, On Hold, Implemented, Tested, Failed, Completed, and Closed, and, for approvals, Pending Approval, Approved, and Rejected.

A new change request is created as Draft. Unless it is created through the API, auto-assignment then runs on it, and the change request becomes Assigned only when its form names an assignee: auto-assignment picks no assignee for a change request, because the workflow parameter Assignee Load Balancing Method is set to Disable Load Balancing for change requests in the supplied configuration. When the change request 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. The form "Create New Change Request" has no field for an assignee group or an assignee, so a change request created with it stays Draft with the support group of its service. The form "Create a Change Request" that Create Change Request opens on an incident or a problem has both fields; see Incident Workflow and Problem Workflow.

Starting work does not move a change request to In Progress: Log Work leaves the status as it is, and saving an Assigned change request while you are its assignee does not move it to In Progress either. In Progress is set only by Take Off Hold, Reopen Request, and Cancel Approvals, and by an update received by e-mail through the Mail Connector.

In the Web App, the progress bar at the top of a change request's full form shows six lifecycle stages (see Follow the ticket's progress):

Stage Statuses
Submission Draft, Assigned
Approval Pending Approval, Rejected
Planning Approved, On Hold
Implementation In Progress, Implemented
Review Tested, Failed
Close Completed, Closed

Action reference

Unless a row names other roles, the actions in the table are offered to the Administrator (Full), Administrator (Workflow), Change Request Manager, and Change Request Technician roles. 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.

Action Offered in What it does
Assign to me Draft, Assigned, In Progress, Approved, Rejected, Tested, Failed, Implemented, Completed, when the change request has no assignee or another assignee Opens no form. 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. A Completed change request keeps its completed date.
Assign to... Draft, Assigned, In Progress, Approved, Rejected, Tested, Failed, Implemented, and Completed, and only to the Administrator (Full), Administrator (Workflow), and Change Request Manager roles Opens the form "Assign Change Request" with Assignee Group, Assignee, Comment, and Time Spent, none of them required. The status becomes Draft when the change request is left with a group but no assignee, and Assigned when a new assignee is set; otherwise it stays.
Schedule Work Draft, Assigned, In Progress, Approved, Rejected, Tested, Failed, Implemented, while the scheduled start date or the scheduled end date is empty Opens the form "Schedule Work" with the scheduled start date and the scheduled end date, both required, and Comment and Time Spent, which are not required. An error message stops the action unless the start date is after the change request's submit date and before the end date, and the end date is before its due date. Saves the two dates, logs "Schedule Work" with the comment, and notifies the collaborators; the status stays.
Implement Change, on a change request of the type Emergency, Standard, or Unspecified Assigned, In Progress, Approved, Rejected, Tested, Failed Opens the form "Implement Change" with Comment and Time Spent, neither of them required. Sets Implemented, logs "Marked as 'Implemented'" with the comment, and notifies the followers and the collaborators.
Implement Change, on a change request of the type Minor Assigned, In Progress, Approved, Rejected, Tested, Failed Opens the form "Add a Comment", which requires a Comment. Sets Implemented, logs "Marked as 'Implemented'" with the comment, and notifies the followers and the collaborators.
Testing Completed, on a change request of the type Emergency, Standard, or Unspecified Assigned, In Progress, Implemented Opens the form "Document Testing Results" with Testing Results, Comment, and Time Spent; Testing Results is not required. Sets Tested when Testing Passed is chosen and Failed when Testing Failed is chosen; with no choice, the status stays. It is not offered on a change request of the type Minor.
Complete Request, on a change request of the type Emergency, Standard, or Unspecified Assigned, In Progress, On Hold, Approved, Rejected, Tested, Failed, Implemented Opens the form "Add a Comment". Brings the change request to Completed and sets its completed date if it is empty.
Complete Request, on a change request of the type Minor Assigned, In Progress, On Hold, Implemented Opens the form "Add a Comment". Brings the change request to Completed and sets its completed date if it is empty.
Close Request Completed, and only to the Administrator (Full), Administrator (Workflow), and Change Request Manager roles Sets Closed, logs "Marked as 'Closed'", and sends notifications. The form requires a Closure Code.
Place On Hold Draft, Assigned, In Progress, Approved, Rejected, Tested, Failed, Implemented Opens the form "Provide a Reason" with Comment and Time Spent, neither of them required. Sets On Hold, logs "Marked as 'On Hold'", and notifies the followers and the collaborators.
Take Off Hold On Hold Opens the form "Provide a Reason" with Comment and Time Spent, neither of them required. Sets In Progress, whatever the status was before the hold, logs "Taken off 'On Hold'", and notifies the followers and the collaborators.
Reopen Request Closed Opens the form "Reopen Change Request", pre-filled with the change request's assignee group and assignee, with Comment and Time Spent; the assignee is limited to the members of the chosen group. Logs "Change Request was Reopened" and sets In Progress, then Draft when the change request has a group but no assignee, or Assigned, with an e-mail to the assignee, when the assignee was changed. Clears the completed date and the closure code.
Mark Duplicate Every status except Closed Opens the form "Mark Request as Duplicate", which requires Duplicate of. Closes the change request with the closure code Ticket Duplicated and relates it to the change request it duplicates; see Mark a duplicate.
Log Work Every status except Closed, and only for the change request's assignee Leaves the status as it is.
Add Comment Every status except Closed, when the change request has no assignee or another assignee The status stays.
Notify Requester Every status except Closed, when you are not the requester The status stays.
Notify Assignee Every status except Closed, when the change request has an assignee other than you The status stays.
Automatic Timer On, Automatic Timer Off Draft, Assigned, In Progress, Approved, Rejected, Tested, Failed, Implemented; Automatic Timer On while the timer is stopped, Automatic Timer Off while it is running The status stays.
Create Work Order Draft, Assigned, In Progress, Approved, Rejected, Tested, Failed, Implemented Opens the form "Create Work Order" and creates a work order whose parent is the change request; the status stays. See Create a work order from a change request.
Create Quick Article Assigned, In Progress, On Hold, Approved, Rejected, Tested, Failed, Implemented, Completed; also the Knowledge Base Contributor and Knowledge Base Manager roles Opens the form "Create a Knowledge Base Article" and creates a related, private knowledge base article at Draft; the status stays. See Create a knowledge base article from a change request.
Create Approval Draft, Assigned, In Progress Creates an approval stage; the status stays.
Request Approval Draft, Assigned, In Progress, Approved, Rejected, Tested, Failed, Implemented, while the change request has a pending approval stage and a pending approval request Sets Pending Approval.
Approve Request, Reject Request Pending Approval, and only for a pending approver of a pending approval stage; on a stage of the Sequential Approval type, only for the first pending approver by rank Records the vote; the status stays. The approval outcome sets Approved or Rejected.
Cancel Approvals Draft, Assigned, In Progress, Pending Approval, while an approval stage is Pending or Pending Approval, and only to the Administrator (Full), Administrator (Workflow), and Approval Manager roles Sets the Pending and Pending Approval approval stages and their pending approval requests to Not Required, and sets In Progress.

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

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

Actions in the Web App

In the Web App, a change request's full form shows these actions on the Action Bar, in these sections (listed here in alphabetical order):

  • Approvals: Approve Request, Cancel Approvals, Create Approval, Reject Request, and Request Approval.
  • Communication: Add Comment, Automatic Timer Off, Automatic Timer On, Log Work, Notify Assignee, and Notify Requester.
  • General: Assign to..., Assign to me, Close Request, Complete Request, Implement Change, Place On Hold, Reopen Request, Schedule Work, Take Off Hold, and Testing Completed. None of them is on the form's toolbar.
  • Relationships: Create Quick Article and Create Work Order.

Collaborators, Copy Request, Follow, Mark Duplicate, and Unfollow are on the form's toolbar only, not on the Action Bar. In a list of change requests, the Actions menu offers these actions too, and each of them except Copy Request can run on several selected change requests at once.

Automatic status changes

  • Saving an Assigned change request while you are its assignee does not move it to In Progress; see Statuses and lifecycle stages.
  • When a change request is completed, its child work orders that are not Closed are set to Completed.
  • When the last of a change request's work orders that is not Closed is completed, the change request becomes Completed. 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 the approval stage created last for the change request is approved or rejected, the change request becomes Approved or Rejected; see Request an approval.
  • A change request that stays Completed without changes for the number of days in the workflow parameter Automatically Close on Change Request Completed (Days) 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.