Issue Summary

It is suspected that after a server-to-cloud migration (which may only affect complex migration scenarios), attempting to create a new space using an existing custom space template fails and returns a generic error in the UI.

Due to one system table missing event type 18, 19.

https://support.atlassian.com/migration/kb/notification-based-on-the-event-type-18-and-19-is-not-supported-via-jcma-migration/

Steps to Reproduce

1. Create a space template from a Team-Managed Software space.
2. Try to create a new space using that template.

Expected Results

The new space is created from an existing template.

Actual Results

In the UI, a message stating that "For some reason the magic didn't happen. Click Create to try again."

The following (please consider this only an example) exception is thrown in the response body of a POST request sent to https://<your-site>/rest/simplified/latest/project (you can verify this via developer tools -> network tab in your browser):

{  
 "message": "No event type with id 18", 
 "status-code": 500, 
 "stack-trace": "" 
}

Workaround

Currently, no workaround is available. Please raise a support ticket if you encounter this issue.