Link and Merge Tickets

On this page

Tickets are connected in two ways. A Work Order can have a parent ticket, and a ticket can be related to other objects on its Relationships tab. You can also merge one Incident into another. For the ticket classes themselves, see Tickets.

Parent and child tickets

Only Work Orders nest. A Work Order's parent can be a ticket of any of the five ticket classes, another Work Order included. In the Web App, you create a child Work Order from its parent ticket's Work Orders tab (see Create a child Work Order), and the parent field on the Work Order form cannot be edited. When you merge an Incident, its child Work Orders move to the target Incident (see Merge two Incidents).

In the Web App

Before you begin

  • A ticket's form is read-only when you may not edit the ticket, and when the ticket is closed.
  • Add Relation, Modify Relation, and Unrelate are disabled while the form is read-only.
  • The Work Orders tab does not show New Work Order while the form is read-only, and an Incident's form does not show the merge button while the Incident is read-only.

Create a child Work Order

  1. Open the ticket that is to be the parent: an Incident, a Service Request, a Problem, a Change Request, or a Work Order.
  2. Go to its Work Orders tab. The tab lists the Work Orders under the ticket as a tree.
  3. Click New Work Order, and choose a create action from its menu. The menu lists the create actions for child Work Orders that are available for the record that becomes the parent.

The form of the new Work Order opens with the open ticket as its parent. If the open ticket's form was itself opened with a parent record, that parent record is used instead, both for the menu and as the new Work Order's parent. The New menu in the form's header does not list these create actions.

Opening a row on the Work Orders tab opens that Work Order's page in the current window, or in a new tab when your setting to open objects in a new window is on. The tab's actions menu also has a delete item, which is disabled when you may not delete the Work Order.

Relate a ticket to other objects

  1. Open the ticket and go to its Relationships tab.
  2. Click Add Relation. The Select object from list dialog opens on All Tickets and lists results at once, unless your setting not to prepopulate select dialogs is on.
  3. To search another class, pick it in the class drop-down beside the search box, and then click Search. Picking a class resets the field filters but does not search by itself; the grid keeps the previous results until you click Search.
  4. Select one or more objects, and click Select. Select is available once at least one row is ticked. Double-clicking a row picks that row, and Enter picks the selected or focused rows. Cancel closes the dialog without picking anything.
  5. In the dialog that opens next, choose the relationship type.

The relationship-type dialog offers only the types available for the classes involved. When you relate several objects at once, it offers only the types available for all of them.

If an object you picked is the ticket itself, a message tells you that you cannot relate an object to itself, and the relationship-type dialog does not open.

In the Select object from list dialog, the class drop-down lists the classes that can be related, limited to those you may view and your license covers, in groups such as Service Desk, Configuration Management, and Groups (which holds All Tickets and All CIs). If you cannot view All Tickets, the dialog opens on the first class of the first group. The dialog also has saved search criteria and an options panel with Activities, Closed, and History switches, a time period, and field filters.

A Problem also has a Related Incidents tab, which lists the Incidents whose related problem is that Problem.

Work with the Relationships tab

The tab shows the related objects as a tree. Its first level has one group row per relationship type, captioned with the type and the number of objects; under each group are the ticket's related objects of that type. Clicking a row's link, double-clicking the row, or choosing Open opens the related object's page in the current window, or in a new tab when your setting to open objects in a new window is on.

To select rows, use their tick boxes, or Ctrl-click or Shift-click them. A plain click on a row only focuses it and clears the selection. Group rows have no tick box. Tick boxes are disabled for rows of a relationship type that a field holds (see Remove a relation), and for the rows that appear below the first level when you expand a related object; selecting all rows passes these rows by.

The tab has these options:

  • Filter narrows the first level of the tree, and the map, to All, CIs, Tickets, or Impact Analysis. It starts on All each time the tab opens.
  • Show only active shows only the active related objects.
  • View as map replaces the tree with a map, and Vertical lays the map out from top to bottom instead of from left to right.

Your View as map, Vertical, and Show only active choices are saved with your user settings and kept on your next visit. The Filter choice is not saved.

Use the map view

Select View as map on the Relationships tab. The ticket is the root; expand relationship groups and objects to follow their relations. A ticket with no relations shows "No data to display".

For opening objects, zooming, keyboard controls, filters, and selecting relations, see View the relationship map and Select relations. The same map controls apply to tickets.

Change a relationship type

  1. On the Relationships tab, select exactly one row.
  2. Click Modify Relation. It is available only while exactly one row is selected. The Relation dialog opens for that relation.
  3. Choose the new relationship type.

When the dialog returns a value, the tree, the map, and the tab's counter refresh.

Remove a relation

  1. On the Relationships tab, select one or more rows.
  2. Click Unrelate.
  3. When asked "Remove selected relationships?", confirm.

When the relations are removed, the tab clears the selection and refreshes the tree, the map, and the tab's counter.

Some relationship types are held by a field of the record rather than stored as a relation, for example an Incident's related configuration item, or the Change Request related to a Problem. Such a relation leaves the Relationships tab when that field is cleared or pointed at another object, by you or by a workflow that updates the field. The tick box of its row is disabled.

In a new 2026.1 database created with the Default Workflow (see Default Workflow Configuration), seven relationship types are marked as held by a field: Associated CI / Associated Configuration, Related CI / Related Ticket, Associated with / Associated Asset, Related Change Request / Related Problem, Related Change Request / Related Incident, Related Problem (Root Problem) / Related Incident, and Associated Asset / Associated Library Item. An upgraded database need not have this content, and an administrator may have changed it.

Merge two Incidents

You merge the open Incident (the source) into a target Incident.

  1. On the Incident form's toolbar, click the merge button. A merge panel opens.
  2. Pick the target Incident. The target search also finds closed Incidents, and a closed Incident can be the target.
  3. Review what the merge will do, and confirm.

In the panel you also choose two things.

How field values are copied from the source to the target. Only source fields that have a value are copied. There are four choices, in this order, and the panel starts on the first one, overwriting only blank values:

  • Values are copied onto the target's blank fields only.
  • No field is copied.
  • Values are copied onto all of the target's fields.
  • Values are copied onto the target's fields that already have a value.

The same choice governs tags. When values are copied onto all fields or onto fields that already have a value, a target that has tags ends up with exactly the source's tags, or none if the source has none. When values are copied onto all fields or onto blank fields only, a target without tags receives the source's tags.

What happens to the source's description:

  • Nothing is done with it.
  • It is appended to the target's description, after a horizontal line in formatted text or after a line break in plain text. When the target's plain-text description is empty, it stays empty; the formatted description is filled.
  • It is put into the merge activity on the target.

Whichever copy choice you make, the field copy never overwrites the target's ticket number or description; only the description choice changes the target's description.

When the merge runs, it:

  • Makes records that refer to the source Incident refer to the target instead, except for the source's activities and history.
  • Moves the source's relations, on both sides, to the target, and makes the target the parent of the source's child Work Orders.
  • Moves the source's attachment links to the target, unless the target already links the same attachment.
  • Adds an activity "Merging tickets", with the details "Merged with <ticket>", to both Incidents.
  • Closes the source Incident by setting its status directly; no workflow action runs. The source Incident is kept, not deleted.
  • When the two Incidents have different requesters, adds the source's requester to the target as a follower.

A ticket's collaborators are people related to it by one relationship type, so the merge moves the source's collaborators to the target with its other relations. In a new 2026.1 database created with the Default Workflow (see Default Workflow Configuration), that relationship type is named Collaborating / Collaborators.

When the merge finishes, the Incident lists refresh and the source Incident's form closes; if the form was not opened from a list, the page then goes to the list. By default, the target Incident opens in a new tab.