Has anyone had to do any transfers regarding the user landscape to get Atlassian ready for provisioning and SSO. Especially with the upcoming Atlassian identity service (add $3 p/u) you have to have everyone in the company domain.
right now we have a large selection of users, manually managed and no proces in place how to name them (usernames), meaning we got firstName, LastName, firstName LastName, nickName in the directory of Atlassian (Jira, confluence and bitbucket) and also a big bunch of externals how have access to whatever but no convention either AND no company domain email.
So to prepare the provisiong (only groups and user creation, because all other options have been turned off by Atlassian when they turned on atlassian cloud) and SSO the following has to happen:
- straight out all usernames to a correct convention - firstName.lastName
- everyone needs a company domain email address
Right now, in my opinion the only way to do this is by creating everyone again and straighten it all out.
PITA but doable.
But than! how do we convert all commits, comments, tickets, issues, bugs etc to the correct user without having to go through everything manually and reassign it all by hand.
Has anyone had to deal with this, and does anyone have an idea, clue or best practise i could follow, im just not able to comprehend the extent of work, time and possible pitfalls i might encounter.
love to hear your thoughts!
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG