Can I report on tickets that were closed by being merged into another ticket? How do I know what tickets were closed by merge?
Closing a ticket by merging it into another existing ticket will add a closed_by_merged tag to the closed ticket. You can report on these closed merge tickets as all existing ticket field data is frozen on the closed ticket.
After you merge and close a ticket into an existing ticket, a note is added to the existing ticket documenting the merge. The only data carried over from the closed merge ticket to the existing ticket is Attachments and Users.
Ticket A is merged into Ticket B. A closed_by_merge tag is applied to Ticket A and Ticket A is closed with all existing data and ticket fields frozen.
The Users and Attachments from Ticket A are added to Ticket B. The agent and end user can continue their conversation in Ticket B. In Explore, the reporting options and restrictions are listed below:
- Explore agents can report on the ticket data of Ticket A by using the closed_by_merge tag.
- Explore agents can report on Attachments and Users information from the closed by merge ticket (Ticket A) that were added to the existing ticket (Ticket B).
- In the merging process, a tag is not added to the existing ticket (a tag is only added to the closed merge ticket). As a result, agents cannot create a report that details what existing tickets have had tickets merged into them. In other words, when reporting on existing tickets (Ticket B), you cannot report on the ticket IDs of the tickets closed and merged (Ticket A) into the existing ticket.
If you are trying to exclude these types of tickets (Ticket A) from your reports, see the article: Explore Recipe: Excluding tickets closed by merge.