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!

Hey Atlassian, I agree this is ridiculous. How are our users supposed to locate other users to assign issues to, when they only know their name (you know, their FULL NAME - the thing that should be populated in the FULL NAME field?) and not their email address? And Administration of accounts needs to be recorded and documented for audit purposes. We do not let users create their own accounts. And we don't let them edit their rights either - that is done by Admins, as well as terminations/removal of accounts. Which is made extremely more difficult if you have to look up their email addresses first. Your systems used to allow the Full Name field to be editable before. Why did this change? You need to change this back ASAP.

+1 to the absurdity of not being able to update a user's full name, especially given the fact that I can't enter it the way I want when I create the user. Why even call it "Full Name" if you are going to put their email address in there and not let us change it? 

Also, I'd like to have the possibiliy to apply the password policies to all my users, whatever their domain is, verified or not, as we had before your designers team decided to remove it (it becomes usual you remove features). I have 80 actives users in our verified domain + more than 80 others (our partners), each in their own domain: I can't ask them to be verified and I have no time to waste in such things. Moreover with the loss of Full name management, they can add what they want whereas we want their company name in the full name.

Voted but I wonder how many votes are required for you to start listening to your customers.

This is a good solution for development teams when one works with several Atlassian products, but terrible for the project teams when I have to manage my customers, very often not very skilled.

Now I lost control of there accounts - full name, private mode when I cannot see full name, etc.
Each time I have to ask them to change name, to re-login in public mode.

Ridiculous... 

I have to agree that this is absolutely a terrible decision. So I can now have users making up whatever name they like? This goes against just about everything I know about Identification, Authentication, Authorization and Access implementations. If I could get my head around any upside...

Related to present issue ,and as some people is saying recently.., there is a new bad decision taken by Atlassian in user management in cloud ,

they have hidden from " User Management section " the " Create user " button where you could set username and Full Name in the  user creation screen.  

For now , as workaround , site administrators can get that creation screen following the direct link,  but it would be very bad if they finally remove that individual user creation screen..

There is a issue reported https://jira.atlassian.com/browse/ID-6417 ,   vote for that to recover the button for site administrators.

I agree that this is a terrible user experience.  An administrator should be able to ensure that the format of Full Name is consistent across all users.  The new default is the user's email address where we have used "FirstName Surname" for every other user in the organisation.  It is a bad experience to ask a new user to the system to change their name.

This is a terrible user experience. As administrators, we need to be able to specify the full name when creating users and to be able to change the full name of existing users.

We need a fix please!!

This doesn't work from two perspectives. Both are terrible experiences and demonstrate how confused Atlassian is about it's value proposition.

One - it's a terrible experience for super users (who are most likely to have multiple accounts - over different instances of the same products, and who this change is supposedly meant to benefit - and who you would want to champion Atlassian products). I used to be able to login in and stay in for a number of Confluence instances (for different clients). Now if I need to quickly check on something while I'm in another instance, I have to logout entirely and then login, then logout, then login - EVERY TIME I swap clients. I used to be able to work on 5 different instances at once and this is now impossible - and very annoying.

Two - it's a terrible experience for novice users. I don't have any users that are interested in finding out how to login to a different system to update their full name. I think there is a fairly basic expectation that as their Administrator, I should be able to do this on their behalf. It is more so frustrating where I need to manage third party access to our Confluence pages and I can't enforce any consistency or naming conventions for user names or full names. If one of my users can't remember their username, I physically have to login in and find them, whereas I used to know their username was firstname.lastname. Now it could be anything! How is that good practice?

Atlassian used to have a great product suite but they no longer seem interested in listening to how their users are actually using the products. I waste a lot of time looking for solutions when others have already raised the issue and there has been no response from Atlassian.

It's even worse than you think https://jira.atlassian.com/browse/JRASERVER-1391. Users have been asking for this feature since 2003, it has 1260 votes on that other thread, and Atlassian have done nothing - actually they made it worse by making it so we can't set the username at all via the default flow in the app.

If a product owner from Atlassian could take a few minutes to look at the extreme displeasure expressed by your users in this and the other thread then that would be fantastic. Your users are screaming out to you, and being ignored. Again.

I guess we're gonna have to keep commenting until it gets fixed... 

They're not fixing it - 135 votes, over 100 watchers, and about 70 comments - and they can't even decide whether to Accept it. 

Any news on when it will be fixed?

I just ran into this problem today.  This has a number of negative implications for my business.  

Firstly, we have a security access policy mandated by the licenses that we hold, that we only grant access to accounts where we have complete information about the user.  If I am granting access to my information to a person for whom I have limited information, this is a violation of my company's security policy.  I am going to have to create users with restricted access and only grant them access to other groups when they have finished inputting their information.  This is inconvenient and time-wasting.

Secondly, it seems that I am to pay for these users, but I cannot control how they appear in my system.  

Thirdly, having only an email address by which to reference someone does not give me enough information about who it is I am communicating with.  We can't be expected to remember everyone's email address and who they are simply because this is more convenient to Atlassian.  

We will not allow any new users to access our information with a more complete profile.  

I (and it appears many others) are unhappy with the lack of understanding about how we run our businesses and how this change was rolled out without any consultation of your user base.  This has significant and time consuming repercussions and I am not happy with it. 

@mfitzbaxter, you could have just summed it up with:

"We decided to arbitrarily screw with our customers' user bases without bothering to do any research on how it would affect our customers, their users, or how our product is used.  This approach applies both those that pay us for our product (which we're now charging more for on average) and those that use the product, and we're not going to do a thing about it because 'some of other people in the SaaS space do it'.  P.S. Here's some other random unrelated garbage that is completely off-topic to try and change the subject."    

It would have been a much shorter explanation than the 8 paragraphs you used to tell us the current (unacceptable) situation that we already were aware of (hence, this ticket).  

@mfitzbaxter, that is a ludicrous response to an Atlassian manufactured issue. Stephan Weynicz sums up the ridiculous conversation you're forcing us to have with our users. How can you possibly think that's acceptable? What's even more frustrating is that clearly there is no technical problem with admins being able to set usernames (at least during creation) as you can still create new users using the old "/admin/users/add" URL. How many people need to complain or vote for this issue before you'll listen?

Also, are @ mentions now not working on this board? Good grief.

I need as admininstrator edit users' full name.

Hi,

I have to change a user's full name, but I am unable to.
The user is deactivated, as he no longer works for the company.
But, on the tickets he worked on, only his first name appears
This is bad when we are looking at the JIRA tickets, as we can only see his first name.
Since there are several users with the same first name, I want to be able to update his name to include his last name

Because he is no longer a user, I cannot have him log in and change his name, as an administrator, I should be able to change it

logging in as him doesn't help, since I don't have access to the what the password is.

Please advise what I can do to make the update.

thanks.

...but don't call me Surely...

Well, one of our girls changed her name to Julia Queen of the North - and I really can do nothing about it... 

It's all very well but I wish I could.

The option really provokes to do so

this is really annoying. While it is not a chatroom but a tool to WORK, letting the user change the user name is NOT a good idea

This is frustrating as an Administrator when you click on the Create button it removes the ability to add a full name. However, Thanks to Will McCall his work around works great... 

Atlassian, please understand how aggravating this is to us Admins that have some OCD as I am now getting users that put ALL CAPS, some that do lowercase, and some that just plain do not add there full name.

Out...

Hamilton,

You can still specify the users full name when creating. (/admin/users/add). I have to use that url because I can't find how to do it within the UI anymore. 

@mfitzbaxter: What about a per-instance field for the user's display name, which can be different than the Atlassian Account display name and editable by the site admin?

E.g. an Atlassian Account with display name "Joey Luvvs ♥" could be displayed on a specific company instance as "Joseph Lovesmith".

It seems a recent update has removed the ability to specify the user login or full name when creating a user in JIRA. You can however edit the username afterwards, but not the full name. So this new 'feature' coupled with the lack of ability to change the user full name as an admin makes an absurd situation even more ridiculous. The workaround for JIRA OnDemand to edit the code view and submit works for a while and then reverts. I don't know why I can no longer locate the previous issue that described this problem existing for 10+ years but users have been complaining about this for a long long long time now. Come one Atlassian we need to manage our users and the user name is critical for this - please listen!

@godneva I found that sometimes after changing the name, the user needs to log out and log back in. It would be indeed so much easier if as an admin I can do that change myself!

Hello, Just encountered this problem with Confluence, also it took time to discover the reason, Then I went and asked my users to change his ID - and it changed at HipChat immideatelly, but it still the same at Confluence.

How long does it take before the id changes?

I feel stupid and useless all the way... 

One tool that might be useful for some...

/admin/users/add

I couldn't find this url in the UI but it still exists. You can set the users Full Name upon creation manually, however they could still change it. Slight work around that may help some.... 

Hey Mike Fitzbaxter its pretty lame that project administrator(s) can't change the name of project user(s). Anyone who works with remote teams knows that getting everyone on board is like herding cats. This change makes administrators look inept, which is a terrible sales pitch for adoption rates.

Let me put it another way:

Project lead: Hi could you please update your display name?
Consultant: sure can't you do it for me?
Project lead: well...no...I mean Jira made some new upgrades and your account went private...
Consultant: can't you just change it back?
Project lead: i tried...but the system is cloud based...and I read this open ticket that your email domain--
Consultant: ok I'll get to it

[three weeks later]

Project lead: Hey did you update your name?
Consultant: I couldn't figure it out. Can't you do it for me?

Hi mfitzbaxter,

This is false that site administrators can change "Full Name" of users whose email belong to our verified domain.

If this kind of users have set their profile as "Private" site administrators  can't edit users details .. Atlassian must correct it.. there is a open ticket for that : https://jira.atlassian.com/browse/ID-6341 , that is unassigned yet! 

Hi, mlavigne - the intention of the feature is that an Org administrator will have visibility and control over their user's accounts. If this is not how the Domain Claimed users are behaving that is certainly a bug and will need to be addressed. There is a ticket raised for this feature request here: https://jira.atlassian.com/browse/CLOUD-10055 which would be a good one for you to follow.

Mike,

I'd guess I saw this coming when I commented the following a week ago:

ago.https://jira.atlassian.com/browse/CLOUD-9469?focusedCommentId=1553939&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-1553939

I've purchased the JIRA cloud solution for my company so we can manage our employees and consultants.   If Giving the ability for an individual the to use the same login across different JIRA cloud instances is one thing.. However, removing the ability for a cloud instance site admin to control the presence of users on his paid site is another.

Hi Mike, thanks for your response. I appreciate you taking the time to explain, however, this really doesn't tell us anything we don't already know, nor does it in any way address the issue. Many of us are not in a position to be able to claim domain names for various reasons. I might be wrong, but reading between the lines here it seems that Atlassian have no intention of actually resolving this, is this correct? At the very least we should be able to override the user's full name in the application that we administer. This is really unacceptable.

This is not true. We have claimed our domain and we still can not edit all our users under that domain. They default to private and if the user doesn't change it we can not edit. This does not work for an enterprise. Administrative nightmare.

Hello everyone and thanks for the comments on the new way that Atlassian account works for our cloud products.

With the recent migration to Atlassian account we made a few core changes to the way that accounts are handled and behave with regards to sites and administrators. The biggest of these changes was to elevate all user accounts to become global across all our cloud products. This change removes the need for a user to have multiple logins to access multiple sites they may be invited to, or to access their content within Bitbucket and HipChat. Users now only need to have a single account to be able to move freely between Atlassian products and this mirrors the behaviour of many other SaaS applications in market today.

A consequence of this shift is that the owner of each user's account now needs to be the user themselves. The information that the user maintains about their global account is visible on all their cloud sites and Atlassian cloud products, so a field like their Full Name will be reflected everywhere that user goes. The same is true for the user's avatar image.

As this change was a forced migration, there were some circumstances where a user had information across their multiple accounts that was not consistent. In some instances a user may have had a different Full Name between their many accounts. It was impossible for Atlassian to know during the migration process which full name the user would like to keep, or which full name they would like to keep hidden from certain sites they had been invited to. In some cases, we discovered that users had deliberately hidden their real name from sites where they were contributing content to protect their privacy.

For this reason, where we identified a mismatch of the user's information we placed the user into Private Mode, hiding the user's information until they access their account and can be prompted to change their display information to whatever they will be happy displaying globally across all products. We completely understand that this has changed the way they display within sites that they are already members of. We would suggest you reach out directly to any impacted users that are invited to your content and ask them to consider updating their display name.

Atlassian account, as part of the migration process also introduced the ability for an administrator to "claim" a domain which they own, and as a result regain control over accounts that belong to that domain. When a user is able to prove ownership of a particular domain name (e.g., foo.com) they gain the ability to edit the details of all users who have an email address belonging to that domain (e.g., gavin@foo.com). This process ensures that only a company (Org) administrator can manage the users that belong to that organisation. Anyone who is invited to your sites that does not belong to that organisation will not be editable.

Over the coming months we will be introducing a number of additional security features to further protect the way that users access Atlassian products which can be used to ensure that users invited to your content are not compromised (such as Multi-Factor Authentication).

If those users belong to your organisation or share an email domain you own we would suggest you consider completing a domain claim to enable Organisational administrative tools such as profile editing and password policy. You can access domain claim tools from within Site Administration.

I know it was possible in the past. We used to add the company name after the family name to easier identify where someone is beloning to in project collaboration. Since some time this is not possible anymore and I would urge to prioritize a solution to trhat. thanks

All these problems started when they introduced Atlassian Account. Who ever is the architect of that should move on as they have no idea how to implement it.

@mention is one thing (and you're right it is a major hassle).  this is even more basic that.  JIRA is a ticketing system and it is hard for people to find the right people to assign a ticket to them.   Epic mess.

Running into this issue daily. Every time we add a new user (we use SAML and claimed domain), their profile is set to private and we can not update their full name. This is BRUTAL. Its making an absolute mess of our user database and its making it REALLY hard for users to use the @mention functionality as no ones first names are populated!

Must have functionality for our organization. 

Very frustrating. I have the same issue with consultants - and with add-ons.

Email from add-ons now comes from indecipherable senders - addon_com.gebsun.atlassian.rtasks (JIRA) <jira@aippublishing.atlassian.net> - but used to come from "Recurring Tasks". I suppose gebsun needs to update their Atlassian account? 

As the admin for my company I originally created an account for a consultant  who left recently.   Before they left they change the name on the account.  I cannot reach that person and that name change appears on hundreds of JIRA tasks.     

I

Some of our users their profile is set to Private when (forced) changing to Atlassian Account - but none knows how/where they changed this?  When you log in onto https://id.atlassian.com and go to Manage your Account : where can you (un)set this?

But still, our company pays for the accounts and decides how accounts are to be used (with domain verification)  I don't see why an user himself should be able to set this company-account as Private? 

Added note :First Atlassian forces Atlassian id upon us (we didn't want nor need that) and starting off 31st of July the licence has gone up more then 200% for us..you really want to loose some clients I guess!

Exactly. We pay for a service to collaborate, and facilitate communication. That service doesn't function properly when we can't be sure who is making contributions.

This will have a commercial impact for Atlassian if they don't address it.

Edit: This is now the #5 highest-voted issue on its board, after four hosting/domain-related issues.

I think this needs to be escalated to someone who understands the severity of the issue rather then someone who will merely reply  "You cannot change someones private Atlassian Account Credentials"

This is really urgent must to have feature for us. Please priorites. 

Hello! I want to be able to add, and edit JIRA users full name. Please! 

This really is an issue. Please enable this feature.

Hi, we really need to be able to add and edit full names of our accounts. Please fix.

Workaround which works: Edit Atlassian Account > logout > login > select "show full name" (don't miss this dialog, it seems to appear only once).

The questions are:

1. why all full names where dropped at some day by JIRA?
2. why user 'sysadmin' has been deleted?

Hi,

I tried this one and worked: go to your profile, choose "Update these details through your Atlassian account." in Account Details. Erase your full name, change field and fill in again the full name. Then Log Out and sign in again choosing "Use my Full Name to display" (or something like that). Change is not appearing immediately but you will see it after 4-5 mins.

hi Dainel,
I tried the workaround of using Chrome Developer tool - IT DOES NOT WORK. any other solution you would like to share ?

Workaround to edit the full_name that I found working:

Right click in Chrome with Developer tool and edit the HTML field for full_name to name you want and click save, seems that it's only locked from editing in front-end, backend seems to store the changes done in field ok.

However If you are using Atlassian Account and need to change a user's full name; You can ask the user to log on to id.atlassian.com and change the name in the Profile. This change will then reflect in JIRA
this solution provided by you does not work, user login & and see all the fields are disabled (non editable)

I also need to be able to change user (JIRA) Avatars while logged in as Admin. I can't do that any more - presumably since the switch to Atlassian accounts.

Our users do not know how to edit their profiles and make their full name visible.

Can someone give us the instructions so that we can help them?

I am an admin on JIRA account and I want to show my full name against different tasks that are assigned to me rather than "admin". Why would you disallow that? Can't there be a checkbox or a setting where an admin can show his/her full name instead of admin?

+1

We got several customers where we use | customername at end of the full names to be able to know what customer it is due to 500+ users

Please do this...

I just noticed that all our users whose full names are showing as just their username have this info bubble saying their profile is set to private. So far I've not seen any exception to that. Unfortunately, this "private profile" feature seems to be otherwise undocumented, and I cannot figure out where in the customer account the user would change that.

WE NEED TO BE ABLE TO SET THE FULLNAME OF A USER

Yes I wrote that in upper case, bold, red text, that's how important it is.

Why in the world would you make our external clients have to go through loops just to set their full name?!

As admins we need to be able to set the full name.

Now we have to beg our collaborators to set the correct name. 

Unacceptable. 

Same as above, this is not helpful in the slightest. We need an option to be able to manually input full name details as well.

We have also tested the proposed solution of asking the user to log into: id.atlassian.com and change the fullname/Display name and it's not being reflected on JIRA. This is just broken. Please, fix it.

As an admin who sets up all users in JIRA (we do not use self sign up) I need to be able to sign up my users with their correct full name. Why was that option taken away? and why do I not have the ability to edit their full name? This has to change because my users are not going to update their names and we are going to start having everyone listed with their user names instead of their names going forward. This is definitely taking a step back Atlassian. Please restore the ability to set up accounts with the users full name as soon as possible. 

I may have a work around. It is a 2 step process. You need to go to the user management click on edit and change the user name and full name to the (same for both) full name that you want display in the full name box. The second step is to go back to the edit screen and only change the user name back to what it was.

ie. (initial credentials) email address: jbrown@example.com - username: jbrown - full name: jbrown

1- (change to-do not touch the email address) email address: jbrown@example.com  username: John Brown  full name: John Brown  

2- (only change the user name): email address: jbrown@example.com  username: jbrown  full name: John Brown  

it worked for me. let me know if it works for you too.

Thanks

Same as comment above. Atlassian ID is terrible for projects with multiple external users. It's one more thing for them to take care.

I add my vote.

Atlassian ID does not work for projects with many external users.

It works for one company only.

I still cannot change the full name in user management. The "workaround" that Atlassian put in the description - to ask each user to change their name - is lame.

It looks like the actual problem changed. For most users I can actually change the full name in user management:

https://your-account-name-here.atlassian.net/admin/users

I am however unable to change external users. Maybe the issue should be updated to reflect that.

I have added a couple of external users to my Jira and configured their access to Jira Core. Since they are external, I would like to add their company name to the full name.

But I can't because they are managed by Atlassian Cloud and from multiple domains which I can't verify.

The only workaround is to individually ask them to change their name themselves. Which is honestly kinda klunky.

Causing a lot of confusion on our side, as many of the full names for our users converted to email addresses or nicknames. Seems like it's updated to whatever name was entered on the oldest Atlassian user record the individual had. Very frustrating.