Skip to main content
Version: Latest
User ManualNeed configuration, code or deployment details? In the Technical Manual: TicketsAssignment and life cycle

Merge and Link Tickets

MenuService Desk > Tickets, then a ticket
PermissionMerge tickets to merge; Edit tickets to link, on the ticket's desk
FeatureTickets
Can't find it?

What you see depends on your role. If the menu, a button or a setting on this page is missing, ask your administrator to give you the permission listed above or to turn on the feature. Only administrators can turn features on and change site settings.

Merge a duplicate​

Merge moves a duplicate into another ticket by its number. The duplicate becomes read only and points to the ticket it was merged into. Its files, and its protected information, move to the ticket it's merged into, and the assignee of that ticket is told.

To merge several at once, select them in the ticket list and choose Merge: they go into the oldest one.

Links relate a ticket to another ticket or to any record, such as an order or a work order, with a relation such as Related or Duplicate. To link two tickets you must be able to see both.

Problems and incidents​

When many people report the same outage, open one ticket for the cause and link each report to it with Its problem under Links. The cause's page lists its incidents (the ones you may see by name, the others counted), and solving it solves every open incident, telling each requester. An incident already solved, merged or only related stays as it is.

Follow-ups​

A closed ticket is read only. When the requester replies after it closed, their reply opens a new ticket that follows up the closed one, so the conversation goes on without reopening finished work.