I'm in the middle of testing a Jira Server to Cloud migration and I've stumbled across something I don't know how to solve so I thought I'd ask you fine folks.
I have taken an xml export of our Jira Server data and imported it to the Cloud instance. I have also setup a trial of Atlassian Access (as we planned to use both Access and Jira Cloud from day one of being in the cloud).
The issue I have is that user names in our server instance are "jseddon" and it looks as though cloud is expecting me to use "email@example.com". I'm ok with this, except I now have a ton of "invalid" usernames assigned to issues that my users will not enjoy.
Has anyone run into this type of situation before? Did I miss an order of operations thing when I was configuring things?
Any help would be much appreciated!
Ok, I thought about this a little more. I'm going to propose a solution to this issue and I will try this out on our test on-prem server. If I were to update all of the usernames in our on-prem instance to be email addresses instead of first initial & last name (i.e. jseddon vs firstname.lastname@example.org) will that get the end result I want where all user field values will correctly map to the users I want when we get to cloud?
I'll try this out and if no one has confirmed before I finish, I'll post my results for anyone looking to do this same thing in the future!
Were you using internal directory or local Active Directory/LDAP?
I'm trying to get this working as well going from AD to cloud with Atlassian Access and am not getting issues to map. I've also tested changing server to use the UPN which will match the cloud email and still no luck.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events