Hi there - we are testing a migration from JiraServer v8 to Cloud and the JCMA (latest 1.9.14) aborts in the pre-migrating-check-phase when trying to migrate one particular project.
The error log lists a number of these error messages:
2023-08-29 17:08:04.941 ERROR <project-key> project-export We couldn't export Issue Security Level Permission 10080. Reason: java.lang.NullPointerException. [JCMA 000]
2023-08-29 17:08:04.971 ERROR <project-key> project-export We couldn't export Issue Security Level Permission 10110. Reason: java.lang.NullPointerException. [JCMA 000]
2023-08-29 17:08:04.977 ERROR <project-key> project-export We couldn't export Issue Security Level Permission 11294. Reason: java.lang.NullPointerException. [JCMA 000]
2023-08-29 17:08:04.980 ERROR <project-key> project-export We couldn't export Issue Security Level Permission 11295. Reason: java.lang.NullPointerException. [JCMA 000]
2023-08-29 17:08:04.984 ERROR <project-key> project-export We couldn't export Issue Security Level Permission 11596. Reason: java.lang.NullPointerException. [JCMA 000]
2023-08-29 17:08:07.967 ERROR <project-key> project-export We couldn't export Issue Security Level Permission 10080. Reason: java.lang.NullPointerException. [JCMA 000]
.....
My question now is - how can identify the specific Permission that is mentioned above so I can remove or change it.
I checked the database tables but couldn't find a table or so that looked like a "Issue Security Level Permission"
Is there some JQL that would lead me to something "human readable" ?
Thanks in advance for any help !
Hi @Christoph Körner ,
Thanks for reaching out to the Atlassian Community, I see you have already reached out to our internal support team and we are looking into this issue via the support request:
We will follow up with you in the support portal and our support team to collect additional details about the errors you are encountering.
Regards,
Earl
Any updates on this? We are encountering the same. Do we have any workarounds?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI,
Overall a surface-level verification, first check to confirm the system version compatibility and if the JVM parameters are configured as covered in the following Doc as this is a nonstandard memory-intensive operation, and running out of memory can trigger a null reference if the app cannot keep up with the DB communication events:
But at the higher level, each instance could be encountering an NPE on many different root causes and narrowing down to a root cause is going to require collecting data unique to each environment
So the recommendation is to reach out to the migrations support team to help narrow down the cause:
Regards,
Earl
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.