Thanks!

Hi everyone, 

Thank you all for your patience. We have shipped a fix that will hopefully solve some of your frustrations.  

An account will never be set to private on the site where it is managed. This ensures administrators can still view and administer all their managed accounts. 

 
The reason that some users are appearing as "private" is that when we upgrade users to Atlassian account, a user could require multiple accounts to be merged. If the profile information differs across the accounts that need merging, the first upgraded account becomes the merged profile. All other accounts with different profile information are made "private" at the site level. This is necessary to avoid revealing this user's private information without consent. 

Only Atlassian can mark an account as private, and only as part of the upgrade to Atlassian account. After the upgrade has occurred, the user can select whether to reveal their profile information on your site when they next log in, or from their product profile page.

Please let me know if this helps.

Helen Xue
Product Management Team - Atlassian

...and they should add the ability to vote up a comment.  +1 to Peter Lui-Hing up there.

As others have said. This is only a partial fix - and it is a critical problem.

Administrators MUST have control of the names of ALL the users on their site.

I think Atlassian is forgetting who their customer is.

It is us, the owners of the site, not our users. Why are you severely impeding our business functionality by implementing a feature that we did not request. Please consider swallowing your pride and just rollback...

Hi,

This feature is must needed, please review the priority of this task.

Hi, 

In our case this fix could be a partial solution.

But I think for site administrators is needed  the possibility to rename in our site all user  with access,  even if the user email not belong to our verified domains. For example  as another people say , when a user has set Full Name = username , or the user change his Full Name in their Atlassian account to whatever he want.. is more difficult to find them to add in mentions using @name. 

Thanks

Hi everyone - we are close to shipping a fix for this. Our solution will be to prevent users from being private on the site that manages their account. There are two parts to this - firstly ensuring all future invites do not incorporate the privacy setting within this context, and secondly the bulk-removal of privacy settings of affected users.
Please let me know if you feel this won't resolve your concerns.

Matt Russell
mrussell@atlassian.com
Product Management Team - Atlassian

Our user database is quickly growing out of control as we are unable to change user's names - making them very difficult to @mention.

We also need our JIRA administrators to have the ability to lock user accounts into a "public" state - allowing users to hide themselves is a confusing option in such an otherwise structured system.

This is causing a major impact to our company's workflow as it is difficult to assign a ticket to someone with an email consisting of numbers and letters that only shows up in @mention after you have typed in the ENTIRE address. Super uncool!

I agree with the above comments, this is a serious design flaw - I need to be able to control all user's names in my instance, not just the ones in the domain I own, but others as well. As the instance admin, I should control Full Name if I want (and could previously, up until this change). I require this control for auditing purposes. One possible bad scenario is if a user renamed themselves to someone else- while I could figure it out, it's a big hassle and would not look good to my auditors.

What they call themselves on id.atlassian.com or someone else's instance is of no importance to me, and should not dictate what's in my instance.

It is a bad design that the holder of a *managed* Atlassian Cloud user account should have the ability to prevent the admins from editing its Full Name. This should not be permitted. We have 16 users where we cannot edit the Full Name field – the field is set to replicate their usernames, and cannot be set to anything else. This needs to be fixed – it is a design flaw and an administrative problem.

 Note that when we try to update a user's Full Name, it seems to work, and a 'successfully updated' message displays on screen, but when we refresh or reload the page, the Full Name is actually unchanged.