This is a dead link:

Claim an email domain:  https://confluence.atlassian.com/adminjiracloud/configuring-domains-868983095.html

This is extremely disappointing. We need to be able to mark customer accounts in our system, as we are an agency. In our On Premise Jira, we used to add (COMPANYNAME) to a customer's user account, so that it's immediately visible that you're dealing with a customer. For example "Gabe Newell (STEAM)" would be a customer's full name. This shouldn't be hard to implement. Even Discord has "Server Nicknames".

Claiming emails domains doesn't work, since the customers may have their own Atlassian Organisation, running their own Jira Cloud.

This issue, as documented, is still not correct.  The above description states that an Administrator with a verified domain can change a managed user's full name and correct their email address. This is not true ** for the managed users in my domain. (I do have administrator access.)

Atlassian account is a single global account that can be used by the users to access multiple sites / Atlassian products, the ownership of account details is either with individual users or with an Organisation.
User profile can be managed by Org Admins by verifying their email domain. For Admins who cannot verify a domain and manage users, we have added a feature for Admins to suggest name / email change to their users which can be found in Site administration >> Users

With the above suggest name change feature in place, we are closing this request.Please feel free to raise this issue again if you feel this issue is still not resolved.

This has been a long standing issue and thank you all for your patience.

Adarsh
Atlassian Product management.

Atlassian account is a single global account that can be used by the users to access multiple sites / products, the ownership of account details is either with individual users or with an Organisation. User profile can be managed by Org Admins by verifying their email domain. For Admins who cannot verify a domain and manage users, we have added a feature for Admins to suggest name / email change for their users under User management / Users.

• Atlassian Product management

I was using a test account, and now want to change the display name in our cloud jira service desk instance.  I went to id.atlassian.com as my test account, change the public & full names to remove "test" from the name, however , on our service desk instance, the 'test" name still shows up.   Is there a time interval where it takes the full/public names from id.atlassian.com to propagate to the cloud instances?    reading a few other threads about who should be able to edit the name, I understand not letting the Jira service desk admin change the display name, but seems that the end-user changing it via id.Atlassian isnt' working?

thanks,

dwight

I came here from https://community.atlassian.com/t5/Confluence-questions/Correct-full-name-of-user-admin/qaq-p/74176

Admins should be able to change the user names. A lot of our internal reports are based on a correct name entry. Having to manually align the data to get the reports working, is getting to be tiresome.

It's been mentioned in the link above, that one of the reasons Atlassian isn't implicating this option for admins, is because users might use the same login to access other products.

To be blunt, they should have entered their name correctly (according to company policy or whatever agreements there are about that, including common sense using capital letters for first and last names) the first time.

Now we can't change it. Yes, you can ask the user. Some change it (yay), but others you can keep asking. We have several offshore and external users (where I can't exactly walk up to) which do not reply to mails, notifications or chat messages unfortunately, so it's a lost cause trying to get them to change their name.

This should be basic functionality.

Preventing admin's from administrating key aspects of Jira prevents organizations from utilizing this product.  Since the "Full Name" field is used throughout the software to identify individuals in the system, it is a KEY piece of information and organizational standards are imperative for Admin's to enforce.  For example, I have hundreds of users and some change their "Full Name" to something like "Mike" or "SuperPanda"... what if someone chose to change their full name to something vulgar?!?!  This is unprofessional and makes them impossible to identify.  Having to ask users (one-by-one) to manage this themselves, is not only awkward and inefficient, I cannot force compliance.  If we had 10 users, no big deal, but hundreds?  thousands?  Users are granted and revoked site access by administrators, so to give "privacy" as a reason to remove this ability, defies all logic.  I have NEVER seen a system that prevented Admins from administering a system before.

Hi everyone, 

I'm from the Product Management team at Atlassian. We are interested in talking to customers based in the US for our cloud products. We are scheduling customer interviews in July & August. As a token of our appreciation, we will provide a $75USD gift voucher for remote interviews and $100USD for in person interviews in our Mountain View office.

Please go here to signup: https://forms.gle/soK6QLoRuRMmLxcv6

Thanks, 
Matthew Ho
Product Management Team - Atlassian

In our case this is what is happening:
We have client 1 and client 2. We provide them with access to our Jira/Confluence instances.

When we were able to set their names we used a convention to differentiate the clients like this:
User1 (Client 1) - user1@client1_domain.com
User2 (Client 2) - user2@client2_domain.com

This way we could handle situations in which two clients had the same name (of course, with differet email domains):
Name LastName (Client 1)
Name Lastname (Client 2)

Clients go and come.
And now we have a new client with a similar email as one of our previous clients:
name.lastname@client1_domain.com (old client, now an inactive account) - With visible name: Name Lastname (Client 1)
name.lastname@client2_domain.com (new client) - now we cannot set the visible name for new users out of our own domain!

The initial part of the email is exactly the same.

When we try to create the new user, the application automatically assigns him the same visible name as the old user.
It seems that internally, the application uses the username (name.lastname) as the primary key when looking for previous users, instead of the email. So the new user gets the visible name of our old inactive user from another client.

It's is not an option for us to call a user (from client 2) and ask him to change his name (the part in parenthesis) because the application is not working properly and is assigning him the wrong visible name.