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.

You can set a users full name but only from the invite widget when you have less than 5 users. 

This means you can set the name for you first users but not after that. This is maddening.

Just got some survey from Atlas today about chat tools integration and I indicated I would not consider them for anything until they fix other systemic issues such as this one. Be factual and polite if you do the same. Maybe someone will get the message this way?

Just chiming in to say that we need the functionality to change the full name of users as well.

Edit: I've read the workarounds.  This is a basic function and as a site admin I shouldn't have to go through a bunch of steps to be able to add a user and specify a full name or edit them directly from the user admin screen.  Having users update this is not an acceptable solution for a basic user administration task. 

Unfortunately it works only for your DOMAIN, but if you have other users with other domains you can't apply this workaround. Very sad that Atlassian don't pay attention that a lot of Cloud Administrators very angry for that issue, because they can't change full name user according to their companies security policy.

That "workaround" doesn't work if you can't claim the domain; as in: you have suppliers, vendors, contractors, etc. working on projects.  On a side note, until Atlassian designates someone else to respond in this issue, it's probably not going anywhere since Mike Fitzbaxter left Atlassian for a company called Auth0 at the end of last year (note: his account is inactive).  

Only if domain verification is activated will this work.  Thanks for the correction!

To update a new user's*Username* and Full name fields, refer to the Word attachment Cant Change Users Full Name Workaround.docx.  Thanks.

This "un"feature ist getting worse and worse. We are connected to our Active Directory, and the user name in Jira (as well as the other Atlassian products) should match the username in the Active Directory. When this feature was introduced, at least most of the time, the usernames were identical. Now, since the add-user-functionality was removed, the Email-address instead of the AD username is used. We really do not appreciate these changes in tools that affect business rules, and there seem to be a lot of these changes lately.

Any plans on changing this back?

Very unsatisfactory change: lately, a lot of changes come about that change the look and feel as well as the administration of Jira. We rely on being able to set the user name which should match the one in our Active Directory. We are using Identity Manager, and sometimes only the email adress is shown in place of the full user name. Very annoying and disturbing to our users.

If you have ever commented on this and you are still having an issue, please come to this page and read the description. It says

"Feature requests we're considering that relate to this change (please vote and watch those that are relevant to you): "

Please go and vote for the feature that would help you best.

Especially this one: https://jira.atlassian.com/browse/ID-6457 Go. Vote on it now. 

I'd have to say that it's intentional at this point.

They're probably pairing down resources at this point to increase shareholder value.

Don't expect much from them anymore.

Hi guys. This problem is affecting our business. We use the username to identify our customers and provide them with a solution. Failing to change the username is causing a terrible mess. Can you help us?

Best regards,

Stefany

rkern257303189,

You can disable the users (set them to 'inactive') and this way they will not use any license.

Maybe I am missing something but I don't see how the fact that only the users themselves are able to change their own usernames can impact in any way the user count. Can you provide more details on this?

Thanks,
Dario

I think https://jira.atlassian.com/browse/ID-6457 addresses this issue best, I recommend anyone watching here votes for it, since it's quite obvious that Atlassian are not interested in reverting to the previous behaviour.

It seems to me all these changes are designed to allow the user counts to grow, unchecked. This, in turn, makes the price go up considerably.

• Site Administrators can no longer create, manage, or edit accounts

That is stupid. If I am going to manage how my organization presents itself, I should have the ability to set Full name to FULL NAME and not default to the email address of a new user I add. If I contract outside of my organization, I don't necessarily want that subcontractor's personal email address displayed as their user name within my organization in Jira. I can't believe Atlassian would not recognize that as a problem.

I'm getting the feeling this once really cool company with great products is beginning to think of itself as another Amazon - because the latest changes to the product is starting to feel more and more like I'm dealing with Amazon - not a good thing.

This is asinine. I've been using Jira for years and it seems with every "improvement", Atlassian takes a step back into the stone age. There are many, many popular tools in the market today and stupidity like this - a page-plus of steps just to normalize Full Names of users on my system makes me want to look for a new solution. 

NVM  - I'm an idiot! The changes can be made in Administration > Organization & Security.

newbie problems! I spend way too much time figuring this out. Hope it helps others.

Admins need to be able to change the user profile.

Ex: User got married. I need to be able to change the FULL name and EMAIL of the user.

This is really annoying.

+1 we need this

+1 We need this

There should be a duality in this step. User's can add/ change their names but Admins should have a handle on the process to avoid misuse

+1 for ability to chg user full name

+1 on changing user full name .

+1 Need to be allowed to change a Full Name.

+1 here too. In our case it is very difficult to ask a user to go back in and "fix this" on their own.  Most won't take the time to do it.  This in turn "breaks" or creates inconsistencies for several important views / pages where macros are used to display username lists.

We have team members who have accidentally added their passwords in the full name fields. The passwords are now exposed and we can't change it ourselves, and they can't change it either (because they're managed accounts).

+1 - editing users' attributes in sys admin 101.

Seriously, how stupid do you have to be to mess up simple administration.  As an admin I should be able to change people's names and/or email addresses.  That I can't do either of this literally vital administrative tasks is unacceptable.  What kind of absolute morons are running the UI logic team?!

One thing you guys seems to have completely missed is that in a large organization, there may be many cloud instances thatl need to be managed independently, even though the users share the same email domain. With SAML this is a nightmare. I have to go to a different department to get them to administer my user list. This needs to be fixed. I don't know if there's a separate JIRA item on this.

Additionally, the inability to edit the users name (User real name) except by asking same said user to do it is lame.

This is interesting - I noticed some updates in the Audit Log. Looks like the 'friendly' user name for the add-ons were changed to the unintelligible ones yesterday:

OPERATION DETAILS:

Date: 10/29/17 9:16 PM (GMT-5) America/New_York
Full name: Recurring Tasks for JIRA addon_com.gebsun.atlassian.rtasks

 
What goes on? When did it go back to Recurring Tasks for JIRA and why was it changed again? 

As an administrator of an organization using JIRA with a lot of customers accounts, which domains are by definition unverifiable by us, i need a safe way to associate a correct name to JIRA accounts and not asking my customers to do so ...

So we have the "Principle Product Manager" come here and tell us categorically that this new feature does not in any way address the purpose of this thread? If you can't understand how much this frustrates us then we have no chance of being heard do we? Thanks mate for proving how little regard Atlassian has for it's community.

pparbhoo - This simple issue has been addressed a number of times in the comments above. A site administrator can no longer edit a user's full name.

From the comments it seems that this simple issue of an administrator being able to edit a user's full name field has still not been addressed directly - a whole year later! Seriously??! 

@Mike Thank you for the detailed response. Unfortunately it is now clear to me that this new feature isn't useful to my business, and doesn't address the title or intent of this thread at all.

You're welcome. You can also vote for this one then: CONFCLOUD-57077 as anonymous users can now see contributor icons, not when reading a page but when clicking on the "Pages" located in the sidebar...

Thanks for that @Bruno Miretti - I've voted for that request as that would be another simple way to solve our problem.  Not sure which would be easier for Atlassian to implement but I would gladly take any option that guaranteed that anonymous users could not get to see our user's real names.

I'd like to add the anonymous users should not see the page author name, an option for this would be welcome. And I could say "would be welcome back" as it was possible with the old UI (details on my post on the request below).

There is an opened request here: CONFCLOUD-37711

@mfitzbaxter

You misunderstand me ... I have NO desire to be able to show a label or some other name IN ADDITION TO a user's "full name", I want something else to show INSTEAD OF the user's "full name" on any content that they create.  What I want is for you (Atlassian) to allow site administrators to CHOOSE whether it is a person's "full name" i.e. as (currently) set by that user, or that person's "user name" i.e. as set by the site administrator, that is displayed on content created by that person on the site controlled by the administrator.  This could be selectable on a per-user basis for each site, or it could be an option for all users on that site: I would be happy to have either solution available, so long as I have control over what happens on "my" site.

Due to the changes that you (Atlassian) have imposed on your customers, it is now the FULL NAME associated with the user's Atlassian account that appears on each and every page that that user has ever created or edited, and on each and every comment or blog post that they have ever made.  Previously, it was the USERNAME as set by the site administrator that was displayed against each user's content.  If a person changes the "full name" on their Atlassian account, that will (currently) immediately affect their name as shown publicly on all content that they have ever created or edited.

Above is how I appear to anonymous users of our instance on a page that I created ... but it is my "Full Name" that is displayed here.  What I should be able to do is to choose (with my site admin hat on) to show my "username" here instead, thus allowing me to use my real name as my "full name" on my Atlassian account.  Logged in users can in any case see my email address (by hovering their mouse pointer over my display name and waiting for the pop-up) and so know who to get in touch with, so they are not inconvenienced by what is publicly displayed. However, it would not matter if it was a user's "full name" that appeared in the pop-up as anonymous users cannot get this pop-up information - nor, incidentally, can they see a user's avatar.

As site-admin, what I NEED is the ability to have full, 100%, TOTAL control of the names that are publicly displayed on our content.  Please ensure that this control is returned to me ASAP.

Thank you.

joe.polastre - The Identity Manager feature is specifically designed to be enabled by a Head of IT or similar within a large organization... the person or team that is responsible already within that organization for assigning new accounts to employees and granting / controlling those employees access to internal and external systems. They are likely the team or person most wanting to enforce a policy or control over employee accounts.

mike.hollingsworth - The feature you are asking for is documented here: https://jira.atlassian.com/browse/ID-6457

This feature could show an additional label alongside a user's name within a site that can be controlled by the admin. This feature is not currently on our roadmap, it would be good to gauge the level of desire from customers for this feature. Please vote on the ticket and follow it for updates.

Replies from Atlassian continue to focus on the side issues and small misunderstandings.

Their continued silence on the main issue (of identity standards when collaborative working between multiple organisations is necessary) leads me to believe their attitude is simply:

"JIRA is not the product for you."

@mfitzbaxter

How are you going to support very large organizations with multiple business units all under one domain? There's no way one person would be authorized internally to manage that entire organization.

2-Factor Authentication is now standard security practice. Requiring 2FA at the organization level should be a standard feature, not a premium upsell.

hamilton4

1. You cannot add users to an Organization that are outside that domain. Any user with an email address belonging to the claimed domain will be added to that organization automatically. Group membership is managed at the Site. When Identity Manager is released in the next couple of months a new admin panel for Organizations will be available showing you all the members of the Organization.
2. See above point - this is not possible
3. We currently do not display the organization that a user belongs to within Site Administration, however this is a feature that is being considered. Feel free to vote and watch this issue here: https://jira.atlassian.com/browse/ID-6448
4. There is no cost involved in creating an Organization and managing the details of the users within that Organization. There is a cost if you wish to apply password policies, enforce 2-Step login, or apply a SAML connection
5. The new user management screens for an Organization will be available when Identity Manager is released into Early Access. All existing users of Identity Manager and Organization features will be migrated to the new interfaces following release.You will see a link to the new admin screens appear within Site Admin following the migration

You will not need to set up users again from scratch. The Org administration screens will allow you to see all users who belong to your claimed domain across all Atlassian cloud products. 

See also https://jira.atlassian.com/browse/ID-6417 

Provided that it was the always the person's USERNAME that was displayed, the person's FULL NAME would become irrelevant to the administrators of any instances that this person had access to.  The person would then be free to choose the name for their Atlassian account, but the administrators can control the names displayed for the users of their instances.

I want to mange my users. I understand that I can now register a domain and setup an Organization using the instructions here https://confluence.atlassian.com/adminjiracloud/configuring-domains-868983095.html. Unfortunately though there is no detail about how Organizations work, and in particular neither Domains nor Organizations are mentioned at all on any of the help pages about managing users and groups. So please tell me, after I have registered a domain:

1. Can I add users and associate them with that domain and manage their accounts 100% including putting them in groups for permissions to access projects, change their user name, and do all the things as admin that I expect to be able to do, or are there some limitations?
2. Can I add users that have email addresses outside my domain or are there some limitations?
3. If I invite users from another Organization to access my JIRA system then can other users see that they are not from my Organization?
4. Are there costs involved with this?
5. How do you migrate from the current user management system to using an Organization - can I just switch all my users over and have their account information and associations with JIRA issues and timesheet records persist?

All I want is to be able to edit user names. I don't want to have to migrate all my users or setup all accounts from scratch and lose all data associations that I user for reporting. I certainly don't want to have to pay more for this. All this seems like a very complicated and annoying way to solve a simple problem. This doesn't seem like the change we asked for and I'm struggling to keep an open mind while I absorb this.

bruno.miretti - Identity Manager will include SAML, Enforced 2FA on managed users, and Password Policy on managed users.

Without purchasing Identity Manager, a user can still claim a domain and update details (name, avatar, email address) of managed users within that domain.

For user's from other domains that feel strongly about needing to have a level of security you can encourage those companies to claim their own domains and enforce the policies that matter to them.

We are currently evaluating the option to apply a 2FA policy on Site Content (enforce 2FA on content) however this is not yet road-mapped.

@mfitzbaxter

Not only have you not answered our problems, but replying on a Friday evening suggests you already knew how poorly it would be received.  This issue has been boiling for one year.  I suggest you re-read all 100+ comments, and try again.

Hi Mike,

please tell us what are the features provided by Identity Manager and remind us what will be for free and what will not be. I saw 3$ per month per user !

I do not see anything in your post that can help me. Creating an organization is interesting but this is good only if you have all your users belonging to this organization. I have more than 80 users belonging to their own (our partners), each with a different domain. How your new features will help me to manage them ?

One year people complain about the problem that severe affects their businesses!!!

After one year of silence, Mike is answering about what the great feature Atlassian unified account is.

No word...

Mike,

I have to agree with Bonnie. Your post is unhelpful and does not address the issues that have been raised here. Please take the time to read and understand the feedback from your customers. This is becoming a major issue for us, and for a large number of others apparently.

Hi Mark - I'm just wondering whether you've read any of the comments Atlassian's CUSTOMERS have been leaving on this site and what they're actual problems are? There's nothing you've contributed here that addresses anything, other than mansplaining Atlassian's poor logic in creating a worst practice Administration experience.

• Claiming an email domain gives me NO control over third parties - and I'm not going to create an email account for a third party so they can exclusively use it to access my instance of Atlassian when otherwise they are using their own email domain. We have lots of independent contractors with access to our instance, and I can't ask each one to use one system to register their domain, and then go into an identity system to manage their user name, and then use an entirely different instance to login to my system.
• Where I personally have different email addresses for each of my multiple clients, I now have to logout then back in for every instance (I didn't have to previously).
• I'm not going to ask my users, who are mostly novices, to login to another system to change their name - for which they can still set it up using anything.
• the list goes on - but as I've said it before, as have many others, Atlassian doesn't seem to be interested in our feedback as this response clearly demonstrates.

The Atlassian Cloud Identity Platform has recently undergone significant changes to enable users to seamlessly move across Atlassian Cloud products (specifically Jira, Confluence, Bitbucket, and Stride). As a result, Site Administrators will experience changes in the level of control they have over cloud users. We understand these changes can be difficult, below I'll provide additional details to help you through this transition. Our ultimate goal is to make it easier for users to move between systems and collaborate together.

The following is now true for all cloud sites and users:

• Cloud users own their own accounts
• Cloud Atlassian accounts are global, allowing users access to all Atlassian Cloud products including Bitbucket, Stride, Jira, and Confluence
• User account information (including full name and avatar) should now be global and consistent on all cloud sites and products, ensuring any changes to user account information will be reflected in all sites and products that users can access

For the reasons stated above, we’re implementing changes to what Site Administrators can and can’t do:

• Site Administrators can invite any user to contribute to their site or revoke user access to their content

• Invited users who do not already have an Atlassian account are prompted to create their account
• Site Administrators can no longer create, manage, or edit accounts

To support customers with specific security requirements you can now claim an email domain and manage all the accounts with an email address belonging to that domain. Claiming an email domain creates an Organization (available in the upcoming Identity Manager release) comprising all accounts who belong to that claimed domain.

Organization administrators can:

• Change a managed account's full name
• Change a managed account's avatar
• Update a managed account's email address
• Enforce a password policy on managed accounts
• Apply a SAML login policy to all managed accounts across cloud sites and products
• Delete a managed account

An organization administrator can't:

• control a managed user's access to a site or product — that is done by the owner / site administrator of each individual site

Next steps:

If you need the ability to manage your organization's user accounts, we encourage you to verify your domain and set up an Organization within the Atlassian Cloud identity platform. As an organization administrator, you’ll have the ability to manage all user accounts within your organization and any changes you make will apply across all Atlassian Cloud sites and products.

If you have users accessing your cloud content from other organizations, you should encourage those organizations to claim and manage their staff's accounts to apply any policies they feel are important to them. You can manage any accounts' access to your content if you're still concerned about the policy applying to those accounts.

Feature requests we're considering that relate to this change (please vote and watch those that are relevant to you): 

• ID-6448 - Show the name of an accounts' organisation next to the account name in Site Admin
• ID-6447 - Show the type of authentication enabled on an Atlassian account within Site Admin
• ID-6443 - Allow site admin to suggest profile field changes on a Personal Atlassian account
• ID-6237 - Allow admin of managed account to change users avatar

There has been movement on ID-6417 that I think looks promising. I've added a comment there, for a tweak to the solution that I think fits us and Atlassian even better.

talking about bugs - do you see a garbled name if user does not have an avatar - see just above Bruno

as for features - I recommend having a look at the KANO model

We already had a price increase of 1.5x compared to the previous year and for less licenses (500 -> 200) and now we should pay to manage our users? and all this for a new "shiny" UI that provides less features than before, more bugs and where navigation is a pain !

Instead of fixing this bug that really impacts peoples productivity and ability to manage their site, Atlassian announces new products that will add a price-tag to currently included features - at least so it seems.

I would much prefer to FIRST have the basic, functioning user management features that people really need and THEN hear about new products and higher prices.

Product Management, please review your priorities!

ahaha it seems that they make bugs so after they can launch a new product and make us pay for it......... we are really thinking of changing and not using Atlassian anymore

yup. Let the gouging begin. Another $3 per user per month.

Please send feedback to the founders on this issue.  I have a ticket open with them CEO-3031.  Atlassian has been uncharacteristically unresponsive to their customers on this issue.   Flood the founders with your concerns!  https://www.atlassian.com/company/contact/contact-ceos

Maybe this is their plan to sell us their new identity product when it comes out.

As a VP of Software Development, if one of my teams created a software solution that did not allow for the updating of a user's full name, they would be fired.  How in the world did the Atlassian Product Owner/Manager believe that this was okay?  It used to work and now it doesn't.  Please don't make the mistakes IBM made by thinking you know more about the users than they do themselves.

As an JIRA admin I want to be able to edit the display name used by any user logging in to mysubdomain.atlassian.net, so that the name can follow the naming convention of my company.

There you go  - next sprint please

I predict Atlassian will do something when this gets to 2000 comments.  Just keep posting!