-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
None
-
Affects Version/s: JCMA - 1.12.36
-
None
-
4
-
Severity 3 - Minor
-
272
Issue Summary
We can address the invalid emails using the advanced experience feature through which we can fix invalid emails via the CSV file. In very rare case, the changes from the CSV is not applied and the migrations fails due to invalid emails at user export stage. Even the preflight checks are passed without any errors.
Steps to Reproduce
- Create the users on Jira with empty emails.
- Have this user contribute to the migrating project
- Assign the correct email address to the user while accessing via JCMA by following the steps from: Customize your users in advanced experience.
- Create a new migration plan including this project and execute the preflight checks.
- Once the checks are successful, execute the migration.
Expected Results
The migration should progress because invalid emails are fixed via CSV by following the steps from Customize your users in advanced experience.
Actual Results
The migration fails at user upload stage and the support.zip shows below error:
2025-07-02 04:55:05,716 JCMA-JCMAExecutorService-pool-1-thread-19 WARN abc.user 289x39482x2 hnnnnn 1xx.xx.xxx.xx:nnnnnn,xx.xxx.xx.xx /rest/migration/latest/check/474aa11bf95b37d53ef7d2d03a63d3cc7c54e2d4 [jira.migration.preflight.PreflightService] (Preflight:88abf132-ff45-4fe3-9475-b44980c8de9b) check execution 474aa11bf95b37d53ef7d2d03a63d3cc7c54e2d4 - fb670923-f4f1-4cb8-8d1f-9cd189d2a467 failed java.util.concurrent.ExecutionException: com.atlassian.jira.migration.httpclient.exceptions.HttpCommunicationException: An error occurred when requesting against HTTP GET https://rps--prod-west2--migration-catalogue--migration-storage.s3.us-west-2.amazonaws.com/mpri/file/scope/93.... ..... .... \\abcnnnjiraprod.file.core.windows.net\xynnnnnprodjira\JIRA HOME\export\migration-to-cloud\checks\ums\474aa11bf95b37d53ef7d2d03a63d3cc7c54e2d4-e9a3754b-f13e-49ba-a47f-90bdaf0dbd4e-invalidEmails.json at java.util.concurrent.CompletableFuture.reportGet(Unknown Source) ~[?:?] at java.util.concurrent.CompletableFuture.get(Unknown Source) ~[?:?] at com.atlassian.jira.migration.preflight.PreflightCheckKt.getUsersFixedData(PreflightCheck.kt:68) ~[plugin . . Caused by: java.nio.file.FileAlreadyExistsException: \\abcnnnjiraprod.file.core.windows.net\xynnnnnprodjira\JIRA HOME\export\migration-to-cloud\checks\ums\474aa11bf95b37d53ef7d2d03a63d3cc7c54e2d4-e9a3754b-f13e-49ba-a47f-90bdaf0dbd4e-invalidEmails.json at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) ~[?:?] . .
Workaround
Manually assign the valid email ID's to the users on the Jira server prior to the migration.