General, flexible, resilent ticketing interface between a device management system and ticketing systems
Systems and methods of the present disclosure facilitate synchronizing data between a device management system and ticketing systems. In some embodiments, the system includes an update module, a mapping module, and a service board selection module. The update module may be configured to update ticketing information about a ticketing ticket on the ticketing system to match device management information about a device management ticket on the device management system. The mapping module may be configured to select a ticket category for a device management ticket on the device management system responsive to the device management information about the device management ticket. The service board selection module may be configured to select a service board for a ticketing ticket on the ticketing system.
1. A system to synchronize tickets between different ticket systems, comprising:
a server communicatively coupled to a first ticket system and a second ticket system different from the first ticket system, the server executing computer-readable instructions causing the server to:
receive, via a ticketing interface from the first ticket system, first ticket information associated with a ticket of the first ticket system;
receive, via the ticketing interface from the second ticket system, second ticket information associated with a ticket of the second ticket system;
compare the first ticket information with the second ticket information;
update, responsive to the comparison of the first ticket information with the second ticket information, the first ticket information of the first ticket system to match the second ticket information of the second ticket system;
identify, based on the second ticket information, a ticket category of the ticket of the second ticket system;
select, responsive to the identified ticket category, a service board for the ticket of the first ticket system;
transmit to the second ticket system, instructions to update the second ticket information to match the first ticket information; and
determine that a modification of an identifier of the ticket of the first ticket system is inconsistent with an identifier of the ticket of the second ticket system.
2. The system of claim 1 , wherein the servers executes computer-readable instructions causing the server to:
identify, in the second ticket information, time record information corresponding to an amount of time for resolving the ticket of the second ticket system.
3. The system of claim 2 , wherein the servers executes computer-readable instructions causing the server to:
update the ticket of the first ticket system with the time record information.
4. The system of claim 1 , wherein the servers executes computer-readable instructions causing the server to:
select a template based on a device referenced by the ticket of the second ticket system; and
initialize the second ticket information based on the template.
5. The system of claim 1 , wherein the server executes computer-readable instructions causing the server to:
repair, responsive to the determination that a modification of an identifier of the ticket of the first ticket system is inconsistent with an identifier of the ticket of the second ticket system, one of the second ticket information and the first ticket information.
6. The system of claim 1 , wherein the servers executes computer-readable instructions causing the server to:
modify, responsive to the determination that a modification of an identifier of the ticket of the first ticket system is inconsistent with an identifier of the ticket of the second ticket system, the ticket of the first ticket system to correspond to the ticket of the second ticket system.
7. The system of claim 1 , wherein the servers executes computer-readable instructions causing the server to:
modify, responsive to the determination that a modification of an identifier of the ticket of the first ticket system is inconsistent with an identifier of the ticket of the second ticket system, the ticket of the second ticket system to correspond to the ticket of the first ticket system.
8. The system of claim 1 , wherein the second ticket system comprises a device management system.
9. A method of synchronizing tickets between different ticket systems, comprising:
receiving, by one or more processors communicatively coupled to a first ticket system and a second ticket system different from the first ticket system, first ticket information associated with a ticket of the first ticket system;
comparing, by the one or more processors, the first ticket information with the second ticket information;
updating, by the one or more processors responsive to the comparison of the first ticket information with the second ticket information, the first ticket information of the first ticket system to match the second ticket information of the second ticket system;
identifying, by the one or more processors based on the second ticket information, a ticket category of the ticket of the second ticket system;
selecting, by the one or more processors responsive to the identified ticket category, a service board for the ticket of the first ticket system; and
transmitting, by the one or more processors, to the second ticket system, instructions to update the second ticket information to match the first ticket information; and
determining that a modification of an identifier of the ticket of the first ticket system is inconsistent with an identifier of the ticket of the second ticket system.
10. The method of claim 9 , comprising:
identifying, by the one or more processors, in the second ticket information, time record information corresponding to an amount of time for resolving the ticket of the second ticket system.
11. The method of claim 10 , comprising:
updating, by the one or more processors, the ticket of the first ticket system with the time record information.
12. The method of claim 9 , comprising:
selecting, by the one or more processors, a template based on a device referenced by the ticket of the second ticket system; and
initializing, by the one or more processors, the second ticket information based on the template.
13. The method of claim 9 , comprising:
repairing, by the one or more processors responsive to responsive to the determination that a modification of an identifier of the ticket of the first ticket system is inconsistent with an identifier of the ticket of the second ticket system, one of the second ticket information and the first ticket information.
14. The method of claim 9 , comprising:
modifying, by the one or more processors, responsive to the determination that a modification of an identifier of the ticket of the first ticket system is inconsistent with an identifier of the ticket of the second ticket system, the ticket of the first ticket system to correspond to the ticket of the second ticket system.
15. The method of claim 9 , comprising:
modifying, by the one or more processors, responsive to the determination that a modification of an identifier of the ticket of the first ticket system is inconsistent with an identifier of the ticket of the second ticket system, the ticket of the second ticket system to correspond to the ticket of the first ticket system.
16. The method of claim 9 , wherein the second ticket system comprises a device management system.