-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Medium
-
Component/s: Operations - Transition JSM/O to JSM
-
None
-
1
-
Severity 3 - Minor
Issue Summary
Some customers, after migrating Opsgenie to JSM Operations, experience a synchronization issue with Operations Teams where the underlying team setup becomes stale, causing the corresponding team to fall out of sync. This prevents proper functionality between JSM and the linked Operations Team.
Steps to Reproduce
- Migrate Opsgenie to JSM Operations
- Have an Operations Team linked/integrated with Jira Service Management
- Over time, the team's underlying setup becomes stale
- Observe that the Team name synchronization between JSM and the Operations stops working as expected, since the team name is different in Operations, but the team identifier is the same.
Expected Results
The integration should maintain synchronization automatically without requiring manual intervention on the Operations Team side.
Actual Results
The team falls out of sync and remains broken until the customer manually updates the team name or description in Operations Teams to force a refresh.
Workaround
Update the Operations Team name or description to refresh the underlying setup and restore sync.