Notification based on the event type "18" and "19" is not supported via JCMA migration
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Check what to do when your Jira Cloud Migration Assistant (JCMA) migration fails with unsupported event types.
Overview
The JCMA pre-migration report has the following messages:
Unsupported <Project> event "18" Custom event type The Notification based on the event type "18" is not supported via migration(custom event issue).
Unsupported <Project> event "19" Custom event type The Notification based on the event type "19" is not supported via migration(custom event issue).Event types archived (ID 18) and restored (ID 19) are associated with the archived issues concept in the Jira Server and Jira Data Center.
The Jira Cloud doesn't have the concept of archived issues, so JCMA can't support the migration of these events.
Solution
This message is just letting you know that this data is not going to be imported into Jira Cloud, so there is no action to be taken on the events.