Creating a New Customer in Jira - for Portal only access creates User Name as qm:013a9b92-fcc3-423a-

[Chris]

Adding new Users - have added users with Email address with no issues - some are coming up as: qm:013a9b92-fcc3-423a-b375-8a574cc03cb3:5 instead of Username@email.com

Am I missing something ?

[Glauco]

Hi Chris,

This feature is something we rolled out as apart of the GDPR changes, you can find more information about this on the Portal-only customers have a randomly-generated username blog post. 

Please let me know if you need any further information.

Glauco Guimarães

[Craig Castle-Mead]

We've just been hit by this "feature" when migrating from Cloud to Server. The export has the external_id as qm:hash:hash - which is 64 characters long, when this gets imported in to a server environment, the CALLER field in the OS_HISTORYSTEP table is a varchar(60), so this caused the import to fail.

Our current fix was - calls all based on MySQL and Jira 7.12.1:

1 - change the CALLER field in the OS_HISTORYSTEP table to handle the longer text - ALTER TABLE OS_HISTORYSTEP CHANGE COLUMN CALLER CALLER varchar(90); - this gives the field enough space to import the usernames with the qm: format

2 - run the import

3 - SELECT lower_email_address FROM cwd_user WHERE external_id IN (SELECT DISTINCT(CALLER) from OS_HISTORYSTEP WHERE CALLER LIKE "qm:%");

The output from the SQL in 3 is a list of users we then converted from Portal only to "full" accounts. This changes their username format to the non qm: structure, which we're hoping (running an export so we can reimport and validate) will allow the import and full history association.

CCM