You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I am trying to test migration path for an app, but I encountered a blocker. Migration fails on use migration phase with an error shown on in the screenshot. Migration fails instantly.
This issue occurs on fresh Jira Server and Jira Cloud instances. There's one simple project and one admin user on the whole instance. Migration fails with "One or more users have an invalid email address" error message. However, all pre migration checks pass.
Furthermore, I was trying to use different domain in email - correct and dumblike 'localhost.com' or 'domain.com'. None of those don't work.
I think, the error message is incorrect, but I haven't found any interesting things in Jira logs. Even if I enabled DEBUG level logs for `com.atlassian.jira.migration` classpath.
Any ideas how to fix that issue?
- Jira server: tested on v8.20 and v8.0.0
- Jira Cloud Migration Assistant: tested on v1.6.7 and v1.6.6
It's been long time since I described the issue. Finally, I managed to resolve that with Atlassian support help.
As I assumed an error message was misleading and the issue doesn't even relate to users' email addresses. The problem was caused by missing SEN on Jira instance.
For development and testing purpose we use timebomb license and it turned out that one of them doesn't generate SEN for an instance. However, “10 user Jira Software Data Center license, expires in 3 hours” license generates SEN and migrations go smoothly now. If you will ever encounter this issue, you can check your SEN here: "/plugins/servlet/applications/versions-licenses" - if it's empty you should change license.
Here is official ecosystem ticket https://ecosystem.atlassian.net/servicedesk/customer/portal/14/DEVHELP-14863
If possible check entries in cwd_user table. There are almost certainly user records with emails that do not match the expected format. These commonly come from external LDAP directories.
there should be a detailed log