-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
Component/s: Cloud to Cloud Migrations - Jira
-
None
-
5
-
Severity 3 - Minor
-
Jira Software
-
Accessibility
Issue Summary
- Jira Cloud to cloud project migration failing with below error
Migration of Project failed. Reason: IllegalArgumentException: Project permission [ari:cloud:ecosystem::extension/b1289a76-*******-b28837364c54/0c5c71a2-237d-4032-a779-b4bdf0b90985/static/RELEASE_MANAGER] does not exist. This permissionScheme isn’t present or referenced in the database. This caused 108264 other items to fail.,Contact support at https://support.atlassian.com/contact/
- This error can occur if some apps [3rd party forge/ecosystem type] are installed on source instance but not installed on destination cloud site.
Steps to Reproduce
1. Install "Release manager for jira" app on source site but not on destination site.
2. Try migrating one of the project from source to destination [using copy data feature].
Expected Results
- Project should get migrated or there should be pre-flight check if any apps are missing on destination source site.
- Proper error message should be given on UI about missing data.
Actual Results
- Project migration fail with below error [available in Post migration report]
Migration of Project failed. Reason: IllegalArgumentException: Project permission [ari:cloud:ecosystem::extension/b1289a76-*******-b28837364c54/0c5c71a2-237d-4032-a779-b4bdf0b90985/static/RELEASE_MANAGER] does not exist. This permissionScheme isn’t present or referenced in the database. This caused 108264 other items to fail.,Contact support at https://support.atlassian.com/contact/
Workaround
- We recommend that your destination has the same apps as your source. These apps may either be Marketplace apps or apps you might have built and installed.
- Install same app on destination site and retry the migration.