Hi Milan,
I dont believe that would be able to be done unless the data itself were copied both ways every time an update was made to one or the other. That would have to include the activity log entries for that ticket, the ticket itself, the notification log etc. And on top of that, both systems would need to also have the same exact reference data with the same IDs for things such as organization, department, location, any CIs, contacts etc. .. any fields from other tables that are referenced by that ticket. It gets even more complicated if tickets have SLAs, contracts, events that fire at certain times, workflow tasks etc, as those would also need to be brought over. So this gets a quite complex and tricky. Unfortunately Service Desk just was not really built for this type of integration. It would require a TON of queries with joins to push and pull data, which would affect the performance of the system and could cause all sorts of errors and problems.
Anyone out there ever get something like this to work? Any insight you can offer to Milan?
Thanks,
Jon I.