Workflow

How to Join Tickets

Verified with controlled creation. Two disposable tickets were created, joined through the list bulk endpoint, the surviving ticket was checked, and the disposable records were cleaned up.

Evidence Summary

Workflow run
ticket-merge-20260519T135959Z
Primary ticket
188 / SUP-2605-58575
Secondary ticket
189
Final state
Primary ticket kept and trashed after verification; secondary ticket URL no longer resolved after merge.

Ticket join workflow diagram

Join Selected Tickets

  1. Open Tickets then Tickets.
  2. Select at least two ticket rows.
  3. Click Join.
  4. Confirm the prompt. OfficeGest warns that the action cannot be undone.

The verified endpoint was tickets / MERGE_tickets, posted as list[]=188 and list[]=189. The response returned {"success":true,"message":""}.

Observed Result

The first selected ticket was the surviving ticket. After merge, ticket 188 kept subject AI Demo Ticket Merge Primary 20260519T135959Z and its detail contained both the primary message and the secondary message AI verified ticket merge secondary workflow. Opening ticket 189 after merge showed The specified file was not found.

Cleanup used UPDATE_ticket with data[is_trash]=1. Ticket 188 returned normal ticket metadata; ticket 189 returned {"success":true,"id":"189","ticket":null}, consistent with the secondary record being absorbed by the merge.

Artifacts