A workaround is to use the browser's developer tools. In Chrome:
Well.. so I wanted to to and audit and change full name of couple of employees because in full name "login" was put.
Now i can;t do that as i would mean i have to delete their accounts and create new ones- this would destroy everything for that user
So why we can;t do that?
I think you mean this: https://confluence.atlassian.com/cloud/organization-administration-938859734.html.
But that only works in the rare case (I think) that all your users share a domain in their email-address that is within a domain you own (doesn't work with gmail accounts, or if you service a Jira instance for your customers, or if your customers like to use different domains because they like to use their own emailadresses).
It's quite odd that I cannot create new users anymore (like Sam Hall shows above) and that I cannot control the users I have created. Imo a limitation that wasn't necessary. It has nothing to do with security, in fact, it is kind to new users if you can create them with a good display name.
This is what worked for me, since (as you might have noticed) Atlassian moved to a new IAM system. Let the user log in to https://id.atlassian.com/
Change the full name to your desire.
Then wait for eventual consistency. It took a few minutes for the update to percolate.
Do this at your own peril...
Atlassian are enforcing this restriction only client-side. Using your browsers developer tools, you can remove the
disabled attribute from the input field.
You can now edit the Full Name and successfully save it.
This seemed to do it. I originally had my initials as Full Name in Atlassian account, and real full name in Cloud account. When they merged the accounts, they changed the initials to both accounts, which my cowrkers did not appreciate. So I tried to change the Full Name for the Atlassian account, which never (2-3 weeks) relayed to the Cloud side. This saved my day
As administrator I REALLY need to be able to control the display name for new users. Some of our users are external - we identify them by adding the client name to the back of the display name
WHY DID THIS CHANGE - it was perfectly fine the old way
this is very disappointing / not at all user friendly / obvious
To change the full name, you need to be logged in as that user. Once logged in:
1. Click on the user icon and select 'Profile'.
2. On the profile page, click 'Edit Profile'
3. Next to the full name field, select the link for 'Manage in Atlassian Account.'
On the next form you can edit the full name for the current user. Enter the name, Save it, and it may take a few minutes for the change to propagate through the system. A browser refresh may also help.
Okay so I figured out the solution to this. When I had the user that misspelled their name login to their account and go to their profile, the hyperlink for the Atlassian account was not there like it was for me (as pictured). So I had the user go to https://id.atlassian.com/login to login and go to "Account settings" and from there the user was able to edit their full name and save their changes. The user then logged out of Jira Cloud and logged back in and saw that the changes reflected in their Jira Profile. Hope this helps others!
Signing on as a user is not an acceptable response. First of all I would consider this to be a huge security breach especially if I change data that the user technically should "own". The sign on option is nice to check what the user is seeing versus what I might see as admin but I would never change data on what is effectively their view of life.
Applications should have names that are for display only - i.e. stand independent from any other application security.
Emails / sign on user ids can be totally separate entries that remain uneditable.
Display names are exactly what they sound like - they appear on reports / screens only and they can be managed by the user OR by the application administrator
Same issue here. Unable to do anything on the Administrator side, but the user is unable to edit it themselves in Atlassian Profile. I'm wondering if this is a problem with Internet Explorer, which is unfortuantely the enforced browser in many organisations? I can do it in Chrome.
I think the workaround / hack suggested by Jakob is out of date now (or at least doesn't work permanently).
Getting the user to change themselves (along the lines suggested by Joe Lehn) should work though, but I guess that is not what you are after.
For what it is worth, there is a suggestion on Atlassian's public issue tracker about this: https://jira.atlassian.com/browse/ID-6415
Atlassian have responded on comments of that (for example on 11 Jul 2017). That's possibly the best one to watch/vote/comment to look out for updates.
Hopefully someone from Atlassian will come on here and comment.
This should be fixed. I can't run after everyone who only enters the first name when signing in.
Atlassian, why do you change thinks that work? I don't get it.
- I can't delete rooms in Stride.
- The UI of Jira is far less intuitive than before and I have to explain everyone in our company where they can find their stuff
- And now I have to run after everyone if they don't enter their names correctly
This is annoying...
Doesn't matter if it's cloud or not, if I am the admin of the licensed Jira I should be able to change any name to Peanut Butter Jelly and update their pictures to Mickey Mouse. The account does not belong to the user, it belongs to the company that paid for it and I am the administrator of it. The user only USES the account, the PC, the resources. He does not own them, he does not Pass GO, does not collect 200$.
No. You are wrong.
As a user here in community, you are using your Atlassian account. Now imagine that you are using a Cloud Jira for your work as well.
You're saying that you would be happy for me, as an admin here but without any access to your Jira, to change your name on your Jira to "Gabriel Does Not Understand This System Baciu"?
If you want to own the accounts, you will need to swap Cloud to using accounts that you own and provide. This will separate them from other Atlassian systems, and you'll need to provision them yourself, with g-suite or your own SAML solution.
What you said actually makes sense, and now I understand. They own their account and the company owns the platform, which can be one of many they use on their account.
Turns out though, that if the user account is made through a managed domain, that Full Name CAN be changed by the admin :)
That does make some sense.
Still, what does not make sense is that when I am inviting the user to my cloud-based JIRA, and that user does not have an existing Atlassian cloud account, Atlassian cloud does not allow me to set the proper full name. Nor does it do what would make sense, which is wait for the user to confirm they want the account and set up their profile, including their full name, during the sign-up process.
Rather, it creates the user right away (which means company admins can create Atlassian accounts for all sorts of people, which seems like a security issue, or at the very least something that can cause significant confusion), and assigns them a full name which is simply nonsense e.g. full name "Bob Bob" for user "Bob Smith". Said company admin then has to tell each user to go and edit their own profile manually -- and most users couldn't care less about this so they just leave it.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs