Hello There,
There is a very common bug where the user who subscribed to the Cloud instance gets his/her's user created with the username "admin" and most of the time this causes an issue where content doesn't get synced to that user.
MIG-93 - User created with admin username when an instance is subscribed
In this particular case, support will need to take a look and see whether or not this is the case, the problem gets a bit more complicated when content gets created with the "new user", however, it is possible to fix this content user mismatch.
We strongly suggest you create a ticket with the migration support team through https://support.atlassian.com/ please mention the user affected by the problem and the Cloud instance you have imported to.
Just so you know, there are other issues that can cause such problem another common one is when the customer has Jira connected to an external user directory like LDAP or AD, users that are not in the internal directory doesn't get migrated over, which may cause issues like the one you mentioned.
JRACLOUD-71339 - When the users are managed by an external directory in Jira Server, when migrating to Cloud the users aren't migrated.
Ideally, you should be able to extract the users and groups using some SQL queries and provide to support so they can import the users beforehand and guarantee the usernames will be the same in both environments.
But since you already migrated support will need to assist you with this one.
Let me know if that clarifies and if you have any other questions send it over.
Thanks!
Best Regards,
*Daniel Brito*
Atlassian | Cloud Support Migration
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.