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

Thank you Will, that is helpful. @Atlassian would you care to explain how this situation came about and what you plan to do to fix it? You must agree this is silly surely?

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.

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. 

We have the same problem! I as admin, need to have a solution where I can change the users full name.

Yes, this Atlassian ID for me as Administrator is a big step back.
Especially as they switched our cloud to Atlassian ID without permissions from our side.

Agreed. Administration requires the ability to update all user account fields, most especially Full Name. Please make this change a priority.

I dont know the reason why I can see your project. Please fix security holes

Same problem here. It must be changed

I've no comment on the move to Atlassian Cloud but there really needs to be a way to edit the user's Full Name.

Wouldn't say Atlassian accounts are a step backwards because we started using JIRA after the Atlassian accounts feature. But you could say it's still missing some crucial features.

Same here. It's annoying to see users with their full email ID. The powerless admin couldn't change even user's profile...

Just encountered this issue today. My team members signed up and just used their email ID as their JIRA name, so my timesheets don't show their full names. Is there really no way for me, as an admin, to go in and update their profiles?