-
Bug
-
Resolution: Fixed
-
Low
-
None
-
None
-
28
-
Minor
Issue Summary
While migrating JSM project using JSM-JCMA custom JAR, "Change group" associated with Issues fail to export.
This usually occurs when
- Issue at some point was dis-associated from a "Request Type"
- Issue is referencing a "Customer Organisation" that isn't associated with the project being migrated
Steps to Reproduce
WIP
Expected Results
Change group should be exported
Actual Results
The below types of exceptions is thrown in the JCMA error log file:
2021-09-19 11:40:31.369 ERROR DESK project-export We couldn't export Change Group 963XXX (on Issue XXXX-19). Reason: java.lang.NullPointerException: fieldData.changeItem.to must not be null.
2021-XX-XX XX:59:56.437066 ERROR XXXX project-export We couldn't export Change Group 43703 (on Issue XXX-255). Reason: java.lang.IllegalStateException: Entity mri:mig:jira/servicedesk:customerOrganization:4 is expected to be exported, but it was not.
Workaround
We have patched this fix in JSM-JCMA custom JAR v28, this version hasn't been shared to all via the EAP dropbox link. This will soon be done.
If you're blocked due to this export issue only, then reach out to internal teams and use v28 for the interim period.
The next release of JSM-JCMA custom JAR will have the fix for such issues. The release is expected to be made around mid Oct'21
[MIG-819] Change Group failed to export
Hi Team,
We have same error with latest JCMA version [1.6.7], is there ay workaround.
Regards,
Shubham
The issue is fixed and released in JSM JCMA custom jar `v30` and also the marketplace JCMA version `1.6.5`.
@Robert Peterson - I also did the update process when prompted, and it seemed to work, sorry that is not the case for you. I've read somewhere that a new upgraded assistant will be available mid. next month, but that might be too long a timeframe for you. Better to ask the developers as my sources on the matter might not be as strong 
Hope you'll figure it all out soon.
@hardy drachmann - thanks - i was able to uninstall, DL back-version, but then it forces to update to latest when moving through the run so in the end, same result 
.
@RKR84 - re: "mid-Oct" ... is there a more precise date to that? Our original transition was going to be happening 10/16 ... ?
Robert Peterson - https://marketplace.atlassian.com/apps/1222010/jira-cloud-migration-assistant/version-history
(sorry I don't know how to tag people in here, '@' doesn't work for me)
Nevermind, the problem is solved. I don't know why, but the only thing I did was to uninstall the Jira Cloud Migration Assistant, then installed an older version, then started a new migration with same settings as before, the pre-testing fase fails because of the outdated version (of course), then I updated to the newest version again, and somehow this fixed my issues.
We decided to do the Jira Server -> Jira Cloud migration as well. All went fine using the Jira Cloud Migration Assistant, but 2 of our projects won't migrate due to various errors.
The errors have been resolved, but the one mentioned here is still there.
I'm new to this, so could you please provide me with the new JAR, or do I have to take any other steps in order to obtain it?
Cheers from DK.
464caa2cf055 We'd like to investigate the error in more detail. The exact error message and additional logs from the application would really help.
I would request you to raise a support ticket for this issue https://support.atlassian.com/contact/