Work on a Ticket

On this page

You work on a ticket by running its step actions. Which step actions a ticket offers, and in which statuses, is set by your organization's workflow; see Workflow Overview.

Start with the everyday tasks below if you use the Default Workflow. The later sections explain the rules shared by the Web App and Mobile App, then describe working in each application with your configured actions.

Default Workflow tasks

Default Workflow: The action names, statuses, and values in this section are those of a new 2026.1 database created with the Default Workflow; see Default Workflow Configuration. An upgraded database need not have this content, and an administrator may have changed it.

In this configuration, there is no general status-change action; you change a ticket's status with named actions. The statuses in which each action is offered, and what the action does, are listed for each kind of ticket:

The tasks below are written for the Web App; for where the actions are on a ticket, see Find a ticket's actions. In the Mobile App, you run the same actions from the ticket's Actions page; see Do these tasks in the Mobile App.

Assign a ticket

  1. Open the ticket.
  2. Choose how to assign it:
    • To take the ticket yourself, run Assign to me.
    • To assign it to someone else or to a group, run Assign to..., choose the assignee group, the assignee, or both, and click Submit.

The status that each action leaves is given on the workflow page of the ticket's kind.

Reply to the requester

There is no separate reply action in this configuration: you reply to the requester with Notify Requester. The action is offered when you are not the ticket's requester and sends e-mail to the requester's primary address.

  1. Open the ticket.
  2. In the Web App, run Notify Requester from the Communication group of the Action Bar.
  3. Type the Comment, add copies, other recipients, attachments or, on an incident or a service request, a knowledge base article, and click Submit.

Its form, "Notify the Requester" ("Notify the Requester via E-mail" on a service request), requires a Comment and offers CC, BCC, and the Other Recipients and Attachments sections. On an incident or a service request, it also offers a Knowledge Base Article, which the requester receives as a link.

On an incident, Notify Requester:

  • logs the activity "Requester was notified" with your comment, in the Communication category, and publishes it, so the requester sees it in the Self Service Portal;
  • e-mails the requester, with the copies and attachments you added;
  • sends the requester a push notification in the Self Service Portal;
  • fills in the actual response date the first time you reply;
  • notifies the incident's followers and collaborators when the workflow parameters turn this on.

When the requester replies to the e-mail, the Mail Connector links the reply to the ticket.

Publish a comment in the Self Service Portal

On an incident or a service request, Add Comment can publish a comment for the requester without sending the e-mail that Notify Requester sends. The Publish to Self-Service Portal check box is not available on the other ticket classes.

Add Comment is offered in every status except Closed, but only when the ticket has no assignee or is assigned to someone else. It is not offered to the ticket's assignee; to record your work as the assignee, see Record work and time.

  1. Open the incident or service request and run Add Comment.
  2. Enter the Comment and select Publish to Self-Service Portal.
  3. Click Submit.

Notify the assignee

Incidents, problems, change requests, service requests, and work orders carry two notify actions, Notify Requester and Notify Assignee. In the Web App, both are in the Communication group of the Action Bar.

Notify Assignee is offered when the ticket has an assignee other than you. It logs an activity and e-mails the assignee at their primary e-mail address. On a problem, it is offered only in Assigned, In Progress, On Hold, and Known Issue.

Record work and time

Time is entered on an activity, through the Time Spent field that most actions carry. To record work, run Log Work, or use Automatic Timer On and Automatic Timer Off.

  • Log Work is on every kind of ticket. It is offered in every status except Closed, and only to the ticket's assignee. On an incident or a service request, its form asks for a Comment, which is required, Responded to Customer, Time Spent, and Publish to Self-Service Portal. On a problem, a change request, or a work order, its form "Log your work" asks for a required Comment, Responded to Requester, and Time Spent.
  • Automatic Timer On starts a timer. It asks only for an optional Comment and logs "Automatic Timer was Turned On". It is offered while no timer is running.
  • Automatic Timer Off is offered while the timer is running. It logs "Automatic Timer was Turned Off" with the minutes since the timer was turned on as its time spent, which then counts toward the ticket's totals.

Put a ticket on hold

To pause work on a ticket, run Place On Hold, and run Take Off Hold to continue; on a service request, the two actions are captioned Place on Hold and Take off Hold. The statuses in which a ticket can be put on hold are listed on the workflow page of its kind.

Resolve and close a ticket

Resolve or complete the ticket

  1. Open the ticket.
  2. Run the action for the ticket's class:
    • Incident or Problem: Resolve Incident or Resolve Problem.
    • Change Request or Service Request: Complete Request.
    • Work Order: Complete Work Order.
  3. If the action opens a form, fill it in. On Resolve Problem, select Resolve related Incidents if you also want to resolve the incidents linked to this problem as their related problem. Click Submit.

Close the ticket

Use the following procedure for a resolved incident or problem, or a Completed change request, service request, or work order.

  1. Open the ticket.
  2. Run Close Incident or Close Problem for a resolved incident or problem, Close Request for a completed change request or service request, or Close Work Order for a completed work order.
  3. Choose a Closure Code and click Submit.

On every kind of ticket, the close action changes only the ticket itself: its work orders and approvals stay as they are, and no warning appears when the ticket still has open work orders.

Reopen a ticket

  1. Open the Closed ticket.
  2. Run its reopen action, such as Reopen Incident or Reopen Problem.

Find out why an action stops on an e-mail address

When you run an action that sends an e-mail, it checks the primary e-mail address of a person on the ticket, such as the requester, the assignee, an approver, a follower, or a collaborator, or of a person you chose on the action's form. When that address is blank, the action stops with the message "<full 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: no status change, no activity, and no e-mail.

The check is part of the action, not a condition for offering it: the action is offered, and you fill in its form, before the check runs. Your own address is checked only when you are one of these people.

Whose address an action checks:

Action Address checked
The resolve or complete action (Resolve Incident, Resolve Problem, Complete Request, Complete Work Order) The requester, and the requester of each of the ticket's work orders that the action completes. The close action does not check the requester.
Every action that changes the status, and Add Comment Each active follower and each active collaborator of the ticket. On an incident and a service request, most actions check only the collaborators who are technicians.
Assign to... and the reopen action Also the assignee who is e-mailed about the assignment.
Notify Requester The requester, the assignee if that is not you, and each person in CC and BCC. On a problem, when Notify Incident Requesters is selected, also the requester of each related incident.
Add Comment Also the assignee, when the ticket has one. On a problem, the requester instead of the assignee.
Notify Assignee, the duplicate action, and, on an incident, Mark as Major Incident The assignee, when the ticket has an assignee other than you (on a work order, whenever it has an assignee), and each person in CC and BCC. On a change request and a service request, the duplicate action checks the assignee of the ticket you chose. On a problem, these actions check the requester instead of the assignee.
Send Meeting Request Each person in To, CC, and BCC, and every active collaborator of the ticket.
The approval actions The approvers who are e-mailed.
Escalate Incident The technicians you chose and those in CC.

On an incident and a service request, other actions check the collaborators too, such as Notify Requester, which checks every active collaborator, and Log Work, Notify Assignee, and Escalate Incident, which check only the collaborators who are technicians. On these two kinds of ticket, Add Comment is one of the actions that check only the collaborators who are technicians.

Followers are checked while any follower notification is turned on, even when the notification for this particular change is turned off, and collaborators while collaborator notifications are turned on. In the supplied configuration, all of them are turned on. So a ticket whose requester has no valid primary e-mail address can be assigned, put on hold, and closed, but not resolved or completed, and an active follower without a valid address stops every status change of the ticket and Add Comment.

Start a TeamViewer session

On an incident, you start a TeamViewer remote session with the requester with TeamViewer Invite and TeamViewer Connect; see Start a TeamViewer session.

Do these tasks in the Mobile App

In the Mobile App, run the same actions as in the Web App from the ticket's Actions page (see Run an action on a ticket):

  • to assign the ticket, Assign to me or Assign to...;
  • to record work, Log Work, Automatic Timer On and Automatic Timer Off, and to pause work, the hold actions, such as Place On Hold and Take Off Hold;
  • to reply to the requester, Notify Requester;
  • to resolve and close it, the resolve action, such as Resolve Incident, or the complete action, such as Complete Request, and then the close action, such as Close Incident;
  • to reopen a Closed ticket, its reopen action, such as Reopen Incident;
  • to start a TeamViewer session on an incident, TeamViewer Invite, and then, once the requester has authorized the session, TeamViewer Connect.

How actions and time totals work

These rules hold in the Web App and in the Mobile App.

Every kind of ticket has one status that Alloy Navigator itself defines: Closed. All other statuses come from the workflow. A ticket counts as active in every status except Closed. See Tickets.

An action set up without a status list is offered in every status except Closed, and a reopen action is offered only while the ticket is Closed. An action that is set up only for other ticket types, or that is not granted to your security roles, is never offered to you; see Security Roles.

A ticket's time spent is the sum of the time recorded on its activities. Its cumulative time spent also adds the activity time of every work order below it, at any depth. When an activity is deleted, its time is taken out of both totals.

In the Web App

Find your tickets

My Tickets lists the open tickets assigned to you or to a group you belong to. A Closed ticket never appears in it, whatever view or filter you use.

Find a ticket's actions

On the ticket's full form, the step actions are on the Action Bar, the panel on the right side, grouped in sections, and on the ticket's toolbar, as the workflow places them. Toolbar actions that do not fit move into the More menu. Unless you pin the Action Bar, clicking away from it hides it and leaves a vertical Actions tab that brings it back. On the preview form, the Action Bar opens in a drawer.

In a ticket list, the toolbar's Actions menu, for the tickets you select, and each row's own action button, for that ticket, offer the actions in an Actions submenu, including actions that appear only on the Action Bar.

An action that is not valid in the ticket's current status, or whose conditions the ticket does not meet, is hidden or shown dimmed, depending on a system-wide setting; unless an administrator changes it, such actions are hidden. An action set up only for other ticket types is hidden whatever the setting. For the rules that decide which actions a ticket offers, see How actions and time totals work.

Run an action

An action that needs input opens a form, and an action with several steps opens a wizard with Back and Next. Click Submit on the form, or on the last step of the wizard. A mandatory field carries an asterisk beside its caption, except a Yes/No check box, which shows none. If a mandatory field is empty when you click Submit or Next, the field shows "This field is required.", and the action does not run or the wizard does not move on. A mandatory attachment area needs at least one attached file. See Perform Actions on Records.

While the form is open, it checks every 60 seconds, while the browser tab is visible, whether the ticket has been changed since you opened the form, and then shows a banner above the fields. If the ticket was changed or deleted after you opened the form, submitting is refused with "You cannot perform this action because the object was modified by another user or process." and the form stays open. Close the form and start the action again to get a form with the ticket's current values.

Edit the ticket's fields

On the ticket's full form, a mandatory field carries an asterisk beside its caption (a Yes/No check box shows none), and the form is not saved while a mandatory field is empty: the field shows "This field is required."

Follow the ticket's progress

At the top of a ticket's full form, a progress bar shows the lifecycle stages of its kind of ticket in order and highlights the stage that the ticket's current status belongs to. The stages after it are shown faded. The stage changes only when the status changes, a status that belongs to no stage highlights none, and a kind of ticket without stages shows no bar.

For the stages of the Default Workflow, see the workflow page of the ticket's kind: Incident Workflow, Problem Workflow, Change Request Workflow, Service Request Workflow, and Work Order Workflow.

See time, resolution, and activities

On an incident, a problem, a change request, or a service request, the Performance panel of the General tab shows the time spent, the cumulative time spent, and the closure code. On a work order, these fields are in the Prioritization panel. On a service request, a change request, or a problem, the Prioritization panel holds the service, urgency, impact, priority, response date, actual response date, and due date.

Incidents and work orders keep a resolution text of their own, separate from the notes, and their full form has a Resolution tab.

On an incident, a problem, a change request, a service request, or a work order, the Activity panel is the last panel of the General tab, below the description. See Activity Log.

SLA metrics

An incident's General tab has a Metrics panel. It shows whether the incident was escalated, resolved the first time, overdue for response, overdue for resolution, or reopened, and its response time and resolution time. Other kinds of tickets have no Metrics panel.

These values are filled by the workflow, not calculated by Alloy Navigator itself: the supplied configuration fills them, and with a workflow that does not, they stay empty. See Services and SLAs.

See Link and Merge Tickets.

In the Mobile App

In the Alloy Navigator app, My Tickets is in the My Work group of the home screen, and incidents, service requests, change requests, and work orders are in the Service Desk group; problems are not among the home screen's classes. A ticket's detail page has tabs such as General, Activities, Relationships, Approvals, and Attachments; which tabs appear depends on the kind of ticket.

The app's Actions page lists the workflow actions you can run on the ticket now, and runs the action's form, its checks, and the action itself. The app never lists an action that is not valid in the ticket's current status or whose conditions the ticket does not meet, whatever the system-wide setting for the Web App is. An action form in the app can be a wizard, and you can attach files to it.

Run an action on a ticket

  1. Open the ticket.
  2. On its Actions page, choose the action.
  3. If the action opens a form or a wizard, fill it in and submit it.

For the actions of the Default Workflow, see Do these tasks in the Mobile App. The approval actions also run from the Actions page; see Approvals.