Issue Summary

Notifications configured for "Issue Archived" and "Issue Restored" in notification schemes cause duplication of the notification scheme in the Jira cloud destination during migration. Ideally, when projects are migrated, they should associate with the existing scheme. However, since the "Issue Restored" and "Issue Archived" notification events are not available in the cloud, if they are configured in the source instance, migration will create duplicate schemes for every project associated with the scheme.

Steps to Reproduce

1. Configuring a Notification scheme with "Issue Restored" and "Issue Archived" events.
2. Associating this scheme with multiple projects.
3. Selecting these projects for migration.
4. Resulting in multiple notification schemes being created for each project in the destination, rather than associating all projects with the same notification scheme.

Expected Results

All the projects will be associated with same notification Schem

Actual Results

Multiple notification schemes will be created and assocated with each project

2024-03-18 03:40:03.635	Creating Notification Scheme [W&M Notification Scheme]
2024-03-18 03:40:03.635	Content of the existing Notification Scheme with ID 10109 has drifted. Creating a new one.
2024-03-18 03:40:03.625	Found an existing Notification Scheme with ID [10109] and name [W&M Notification Scheme (migrated 74)] 

Workaround

Remove the Notification for the events "Issue Restored" and "Issue Archived"