Create a Ticket

On this page

A ticket is an incident, a problem, a change request, a service request, or a work order; see Tickets. You create a ticket by running a create action, an action that makes a new record. Your organization's workflow decides which create actions exist, what they are called, which form each one opens, and which values the new ticket starts with; see Workflow Overview.

Before you begin

The create actions you are offered depend on your security roles; see Security Roles. Unlike the actions you run on an existing ticket, create actions are not limited by status or type, and an organization restriction on your role does not narrow the create actions you see. For a support account, the role condition does not apply: a create action restricted to certain roles is offered whatever the role grants say; see Accounts.

A create action can also have an additional condition, set in your organization's workflow. When that condition is not met, the create action is not offered. In the Web App, it is left out of the lists of create actions under New, except that one you used recently still appears under Recent, unavailable; see Choose a create action. In the Mobile App, it is left out of the list that New opens.

In the Web App

Choose a create action

You can start a create action from any of these places:

  • The New... button in the header. Under Recent it can list up to 10 of the create actions you used recently, and More opens the list of the kinds of record that have create actions. When you have no recent entries, that list is shown directly. Pick a kind to list its create actions, with an entry that takes you back to the list of kinds. A create action that holds entries of its own opens them as a further level. Depending on the entry, picking it opens its form in place, opens a side panel, or goes to another page. A recent entry whose workflow conditions are no longer met is unavailable, with the tooltip "This action is not available because the required workflow conditions are no longer met."
  • New on the toolbar of a list. Open the list of the kind of ticket you need from the Service Desk group of the navigation menu: Incidents, Service Requests, Problems, Change Requests, or Work Orders. Click New on the toolbar above the list. Each time you open New, it loads the create actions of that kind: the menu shows "Loading..." while it does, and "No Actions" when there are none. Create actions in a group appear as nested submenus.
  • New on an open ticket. On an open incident, problem, change request, or work order, New on the toolbar lists the create actions of that kind of ticket.
  • New Work Order on the Work Orders tab. On an open incident, service request, problem, change request, or work order, the Work Orders tab has a New Work Order button, unless the form is read-only. It lists the create actions that make a subordinate work order; New on the ticket's toolbar does not list them. The new work order's form opens with the link to its parent already filled in.

Fill in and submit the form

When a create action you run in the Web App needs input, it opens a form, or a wizard when the form has several steps. The form works like the form of any other action; see Perform Actions on Records.

  1. Fill in the fields. A required field is marked with an asterisk; a required Yes/No check box carries no asterisk.
  2. In a wizard, click Next to go to the next step and Back to return to the previous one. Back is unavailable on the first step and Next on the last.
  3. Click Submit to create the ticket, or Submit and open to create it and open the new ticket. In a wizard, Submit appears on the last step.

Required fields are checked when you click Submit or Next, not before. An empty required field shows "This field is required." under it, the cursor moves to the first such field, and the ticket is not created; in a wizard, Next does not move on. After a failed check, a field is checked again as you change it. On a wizard step, only the fields of that step are checked; the workflow can also check the step's values before the wizard moves on. A required attachment area is satisfied by at least one attached file.

Which fields are required is part of how the create action's form is set up; see Actions.

If you cancel a wizard that is still on its first step and in which you have changed nothing, it closes at once. Otherwise you are asked to confirm first.

When a create action opens the full form of the new ticket, fill it in and click Save: the ticket is created and its page opens. Save stays unavailable until you change something on the form. A required field is marked with an asterisk, except a required Yes/No check box, and the form is not saved while a required field that is not read-only is empty; the field then shows "This field is required."

When a create action has a template, its form opens with the template's values already filled in, except in fields that the ticket fills in by itself. A macro or expression in a template field is evaluated when the form opens. The template does not replace a value that the form itself, or the link to the record you started it from, already sets. When you submit, the template fills in a field again only if you left the field empty, and only when the template sets a field that is read-only for that kind of ticket. A value you entered is never overwritten.

In the Mobile App

In the Alloy Navigator app, New is on the bottom bar of every screen.

  1. Tap New. The app lists the create actions available to you, grouped and captioned as on a record's actions page.
  2. Tap the create action you need. It opens as a wizard for a new, empty record.

When you complete the wizard, the app opens the new ticket.

An action form in the app can be a wizard, and you can attach files to it. The app applies the maximum attachment size set on the server.

What a new ticket starts with

  • Template values. A create action can carry a template. The template's values are applied when the ticket is created.
  • The form. A create action uses either the full form of the ticket or a form of its own. A form of its own can be a wizard.
  • The ticket number. Your organization's workflow composes the ticket number and decides its format.
  • The workspace. When nothing sets the workspace of a new ticket, the ticket is placed in the IT workspace.
  • Subordinate work orders. A create action can make a work order as a subordinate of another ticket. A work order can be subordinate to a ticket of any kind, including another work order.

Create actions in the supplied configuration

The names 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.

  • Incidents. The configuration creates incidents through New Technical Issue, New Major Incident, API Incident Creation, New Technical Issue (Self Service Portal), and New Incident (Mail Connector). Each of them creates the new incident as Unassigned. Every one of them except API Incident Creation then runs auto-assignment, which can make the incident Assigned at once; see Incident Workflow.
  • Problems. The configuration creates problems through New Escalation, New Major Issue, API Problem Creation, and New Problem (Mail Connector). Each of them creates the new problem as Unassigned. A problem whose form "Create a Problem" names an assignee becomes Assigned at once; see Problem Workflow.
  • Workspace. The templates of this configuration do not set the workspace of a new record. A create action can set it in its program instead, through a workspace function of the record's class whose default is set to IT for tickets. New Technical Issue, for example, puts the new incident in the IT workspace.
  • Copying a ticket. Copying is an action of an open ticket, not a create action, so it is not listed under New. In the Web App, the configuration places Copy Incident, Copy Problem, and Copy Work Order on the toolbar of an open incident, problem, or work order, or under the toolbar's More menu when they do not fit. Each opens a form of its own, and the copy is made when you submit the form.

Tickets from e-mail and the Self Service Portal