I'm researching migration from Jira Cloud to Server.
When I restore the backup on servers, user end up with usernames like ug:03775bde-ca11-432b-8833-b3cedeadbeef. It appears there is no other username, they cannot log in with email either.
Is this correct? What is the common, recommended workaround to get them to work again, with human-friendly usernames?
Yes it's common as usernames are not applicable on Cloud Instance as they have been deprecated, so during migration from Cloud to Server, You will need to ensure that you define a username in the xml file rather than import it like that (although that method is rather complicated) else, you will see those alphanumeric string on the user. Another way you could go about this, is to create those users first using REST API on Jira Server. Jira Server will auto assign a username to those user. So during your import from Cloud to Server if the email address matches, Jira Server can pick up that user as an existing user.
@Prince Nyeche Thanks, this second option sounds intriguing. However, I could not get it to work. Restoring a backup always seems to completely replace my userbase, overwriting whatever I may have created before.
Can you elaborate on it a little? What exactly are the steps here?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Konrad,
We are migrating from Cloud to Server and are having the same issues as you with the user names.
Can you please let me know how you ended up solving this?
Thanks,
Yemon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Ychambers sealite in our experience there are 3 reliable ways of migrating users:
See also: https://support.atlassian.com/migration/docs/determine-your-user-migration-strategy/
It's getting complicated when you have external user directories - Jira Cloud doesn't support them, you'll have to edit your configuration or manipulate the XML/CSV files so that they only have the internal directory. We ended up implementing our own custom tools to do this (I can't share them here as we're using them for commercial consulting).
Hope this helps.
Konrad Garus/Expium
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Konrad Garus ,
Deprecation notice and migration guide for major changes to Jira Cloud REST APIs to improve user privacy.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks. I know about it, but it doesn't really answer my question about migration to Server.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.