Skip to main content
Rule for ticket split
Albert Basiul avatar
Written by Albert Basiul
Updated over 7 months ago

The split of tickets can be done for various reasons:

  1. Multiple Service Components: When multiple service components are independent from each other, they can be split into separate tickets. This allows for better tracking and management of each component individually.

  2. Different Priority Levels: In some cases, there may be a need to address both a request and an incident in the same ticket. By splitting the ticket, each issue can be assigned the appropriate priority level and handled accordingly.

  3. Complex Issues: When dealing with complex issues that involve a large number of affected objects or devices, splitting the ticket can make the work more productive. It allows for better focus and attention on each individual aspect of the problem, and ensures that constant updates are provided to the customer.

  4. Escalations: If a customer raises a complaint during the resolution of a request or incident, and the complaint is related to the solution, it can be beneficial to split the ticket. This allows the complaint to be assigned to the responsible group for proper handling and resolution.

  5. Ticket was reopened with a new case: If a ticket has been reopened with a new case, it may be necessary to split the ticket to ensure that each case is properly addressed and managed.

NOTE: The ticket can be split into a maximum of four parts due to its complexity. The customer should be informed about this division.

Did this answer your question?