Issue sync service is deployed to BCSM and connects to message events generated by Issue management. It then makes changes in ALIM.
The sync service is therefore hidden from users and an automated job.
Resilience is key to its success including the ability to:
monitor its capabilities (ability to connector various APIs).
Understand what has not been successful.
Audit all actions, especially errors.
Notify users of problems
Retry any failed API attempts.
With all of the above in place it is still possible problems occur. Therefore system must have the ability to retry the syncing of an issue manually by either:
Providing a date range in which issues were created.
Providing one or many issue codes.