Issue Summary

• After initiating the transition from OpsGenie to Jira Service Management Operations, Closed OpsGenie Incidents Migrated to JSM are seen as Open Incidents in JSM underneath their respective Services and are never removed from the Services unless the "OpsGenie Migrated Incidents.." projects are deleted.
• The statuses on the Migrated Incidents retain their Closed status from OpsGenie.

Steps to Reproduce

1) Prior to migrating, a number of closed incidents exist on the OpsGenie instance. Note that they have been closed for several months / years. Some of these Incidents have an Affected Service associated with them (Jenkins for example).

2) Initiate a Transition to JSM Operations

3) Projects are created on JSM containing Incidents migrated from OpsGenie, as expected.
Click on the projects and note all of the closed Incidents inside of them.

4) On JSM, go to a Service Project, click Services, and pull up the details of a Service (in this example, we are using Jenkins).

Expected Results

• The Service should not be seeing any closed, migrated OpsGenie Incidents as Open.

Actual Results

• The Service is listing all of the closed and migrated incidents as open, even though they've been closed for a long time and the Service is not automatically purging them from their Open Incidents lists:
  

• Normally, a Service will eventually remove an Incident from its open list after a few after it has been closed. In this case, the OpsGenie Migration was done two weeks prior, but the Closed incidents still remain on the Open list.

Workaround

• Option 1 - In JSM Operations, reopen then close the migrated Incident tickets. This should cause the Service to no longer see these incidents as open. It may take a few minutes for the changes to be seen.
• Option 2 - Delete the "OpsGenie Migrated Incidents" project(s) if the old Incidents aren't needed.