Create Accountor Login
Docs

Merging Tickets

Part of the MountDev Ops Helpdesk documentation. Updated November 21, 2026

MountDev Ops Helpdesk documentation | Updated November 21, 2026

When one conversation ended up as several tickets, merge them into one, so the whole conversation is in one place.

Our Commitment

MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.

Every update passes all 8,865 automated checks before it ships, and every screen change is walked through before release.

Merging from a Ticket

Open the ticket you want to keep and select Merge in its header. Helpdesk suggests tickets that look like the same conversation (action helpdesk.merge.suggest): the same requester, the same subject (ignoring Re:, Fwd:, and ticket numbers), or the same company, best matches and newest first, each saying why it matches. Search by number, subject, or requester to find any other ticket. Check the ones to merge, or select Check All Shown (up to 200 at a time), read the confirmation, and select Merge (action helpdesk.merge).

There is no limit on how many tickets you merge at once. Helpdesk merges them 20 at a time into the same ticket, with a progress bar. If a step stops, the message says how many were merged, nothing is half moved, and Finish Merging carries on from there.

Merging from the Inbox

Check two or more tickets in the Inbox and select Merge in the bar that appears. Choose which ticket to keep (the oldest is chosen for you), then confirm. The pop up closes, and the kept ticket's row and each merged ticket's row frost over while they work. The merged tickets then fade out of the list and the rows below slide up, and the kept ticket stays. If a step fails, the kept ticket's row says why, and nothing is half moved (Progress on a Row).

What Happens

  • Everything moves into the ticket you keep: every message and internal note, shown in time order, their files, upload links, and replies still waiting to go out.
  • Later replies find their way: when the client answers an email from any of the merged tickets, the answer joins the ticket you kept. So does an email with a merged ticket's number in it.
  • Nothing is deleted: each merged ticket stays, closed and marked Merged into the ticket you kept. It no longer shows in the Inbox or its counts, and opening it shows where it went, with a link. Its automatic follow-ups stop.
  • Requesters: the requesters of the merged tickets are listed on the ticket you kept, under Also on this ticket. Replies still go to the ticket's requester.
  • A note on each ticket says who merged what, and the Activity Log has it too.

One Scroll for a Merged Ticket

A ticket with others merged into it shows every message of every original ticket in one scroll, newest first, opening at the top. The page never scrolls on its own. Each original ticket has its own color bar and a small From line with its number, a day divider separates the days, and several messages in a row from one sender are grouped. A row of buttons above the messages shows each original ticket with its people and message count; select one to see only that thread, and All Threads to see everything again. Show Earlier Messages is at the bottom and loads older messages 100 at a time. Reading never changes the tickets.

Undoing a Merge

For 30 minutes after merging, the ticket you kept shows Undo Merge for each ticket merged into it (action helpdesk.merge.undo). Undoing moves everything that came from that ticket back, opens it with its earlier status, and notes the undo on both tickets. The person who merged, or an owner or admin, can undo. After 30 minutes, use Move to New Ticket on a message instead (Tickets and Replies).

Private Tickets

A private ticket is one that arrived at a person's own private address (Helpdesk Settings). Only that person sees it. These rules decide what it can merge with:

  • With another private ticket of the same person: merges as usual.
  • Into a shared ticket, by the person it belongs to: allowed, on purpose. Before it merges, a pop up says "This conversation will become visible to everyone who can see the ticket you are merging into." Select Merge to go on or Cancel to stop. The merge needs that confirm, so an AI agent, an API key, and the API cannot do it, and nobody but the person the ticket belongs to can. The Activity Log records one line with the ticket numbers (never the words in them), and the ticket you merged into gets a note saying it was merged from a private ticket and by whom. The private ticket stays private, marked Merged.
  • A shared ticket into a private ticket: never, because that would hide shared work.
  • A private ticket of one person with another person's private ticket: never.

In the Inbox, select Merge from a ticket's own page to merge a private ticket. Merging from a checked list in the Inbox does not ask for the confirm and says so if a private ticket is in it.

The suggestion below and the list of tickets in the Merge pop up show Merge only for tickets that can be merged for you. A ticket that cannot be merged says why in one sentence, and a private ticket of yours that can go into this one says you will be asked to confirm.

Suggested Merges

When a new ticket arrives from a requester who already has an open ticket with the same subject, the new ticket shows This looks like the same conversation as that ticket, with a Merge button when the merge will work for you, and otherwise a sentence saying why not. Turn the suggestion off or on in Helpdesk Settings with Suggest merging matching tickets. It is on at first.

Who Can Merge

Anyone who can reply on tickets and change all the tickets involved: owners, admins, and members whose role lets them change those tickets. An admin-only ticket can be merged only into another admin-only ticket. AI agents can find, merge, and undo merges as the person who connected them, with the same checks, except that they can never merge a private ticket into a shared one.

Ask Us Anything

We’d love to hear from you!