We couldn't export Issue Security Level Permission: Server to Cloud 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
The documentation provides guidance on resolving the "We couldn't export Issue Security Level Permission error" that occurs during on-permise to cloud migration using JCMA.
Overview
When attempting to migrate projects from On-Premise to Cloud using the Jira Cloud Migration Assistant, the migration process fails with the following error:
ERROR TEST project-export We couldn't export Issue Security Level Permission 10001. Reason: java.lang.NullPointerException. [JCMA 000]
It indicates that there is a reference to an Issue Security Level Permission in a Jira Issue that no longer exists.
Fix Issue Security Level Permission error
Always backup your instance database before any changes, or first try the changes in a staging environment
Check whether the Issue Security Level Permission mentioned in the error message (ID 10001) exists within the On-Premise instance.
SELECT * FROM schemeissuesecuritylevels WHERE id=10001
If the ID is not found, perform a search for it within the project where it was raised using the database query provided below:
SELECT jiraissue.id , jiraissue.issuenum , jiraissue.security FROM jiraissue JOIN project ON jiraissue.project = project.id WHERE project.pkey = 'TEST';
Verify if there are any issues referencing this ID in the security column in the results of the overhead query. If they exist, simply update the reference to null or to the correct issue security level.
To update details from the database, use the following update query:
UPDATE jiraissue SET security = <either null or right value> WHERE id = <id of the issue seen above>