Removing usernames in JIRA Cloud due to GDPR

[Johan Lindgren]

This item make little to no sense to me. If it is a public forum/free application then that can make sense but in a corporate environment it makes no sense as there has to be abilities to have responsibility and logging for work done as well as keeping track of who did what.

So, I strongly oppose to removing usernames in Atlassian Cloud for paying customers.

https://confluence.atlassian.com/cloud/blog/2018/06/say-goodbye-to-usernames-in-atlassian-cloud

Sincerely,

Johan T. Lindgren

[Scott Theus]

Hi Johan,

Perhaps I'm reading the announcement incorrectly, but it does not seem like Atlassian is taking away any of the site-admin's ability to track changes or of the users to log work under their own identity; rather they are eliminating one of the three fields used for this purpose.

Currently, the user John Doe can be identified as username jdoe1234, display name John Doe, or email jdoe@email.com. It sounds like that with this change only the username jdoe1234 is being eliminated. 

-Scott

[Manon Soubies-Camy]

That's also what I understand:

Atlassian accounts use the email address as the unique identifier

Usernames (...) will eventually be phased out in favor of display names

So you'll still be able to track who did what based on emails and display names.

- Manon

[Christa Lourens]

Does anybody know how to make the  Display Names appear as they should or did? 

Even if I log in as the user I cannot edit the name under the Profile for Full Name fields. 

I understand it needs to be stripped from the API but currently, the return is a bit problematic for us. 

Any new users I now add to our company's cloud has a generic format i.e johndoe81@something.com instead of johndoe@something.com or then just John Doe. 

A new Display name field should be added to either /admin/users/ and /admin/users/view 

or /secure/ViewProfile.jspa