fullName is not getting set while creating User
Asked by dhiman.das:

**Warning:** Before I write anything, if you're going to try the same, it's a request not to use this "@opsgenie.com" domain to create a user. There's a serious issue with your "@opsgenie.com" domain and other domain.

Let's explain you the scenario:

1. I'm trying to create a user, using postman  

![Screen Shot 2020-09-18 at 8.49.15 AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/110851i9A8C17AE2E196991/image-size/large?v=v2&px=999 "Screen Shot 2020-09-18 at 8.49.15 AM.png")  

2. After "created" response, I have tried to do a get by user id, and surprisingly the "fullName" is mismatched. If you notice it property the "fullName" is nothing but the first part of your "username".  

![Screen Shot 2020-09-18 at 8.50.34 AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/110853i9898D3E2DC08243C/image-size/large?v=v2&px=999 "Screen Shot 2020-09-18 at 8.50.34 AM.png")

3. Here's the UI result  

![Screen Shot 2020-09-18 at 8.51.30 AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/110854iCD5C968B02D3AE34/image-size/large?v=v2&px=999 "Screen Shot 2020-09-18 at 8.51.30 AM.png")


Answers:
author: DPKJ
body: I tried it on test domain but it seems to be working fine. Here is command I tried,

```
curl -X POST  'https://api.opsgeni.com/v2/users' -H "Content-Type: application/json" --header 'Authorization: GenieKey <API_KEY>' --data '{ "username": "john.doe@example.com", "fullName": "John Doe", "role": { "name": "User" } }' 
```

Please do replace API_KEY with valid API Key.

comments: author: dhiman.das
body: Thank you for your response. I forgot to mention one more thing, it seems like John Doe is hardcoded or something like that. Can try with something different? Not with "John Doe" and not with the "@opsgenie.com" domain.


author: dhiman.das
body: [@DPKJ](/t5/user/viewprofilepage/user-id/690016)


author: DPKJ
body: I did tried different name, John Doe is just to give you overview.


author: dhiman.das
body: [@DPKJ](/t5/user/viewprofilepage/user-id/690016)Alright. Thank you. I will try with different API Key. But it's happening with every account. Even with enterprise version also.


author: dhiman.das
body: [@DPKJ](/t5/user/viewprofilepage/user-id/690016)I hope you have tried with a random domain apart from your test set. I really feel like something is not right.


author: DPKJ
body: Let me ask someone from Atlassian team to take a look at this. I think this is one of the main API and I don't think if it has bug it will unknown to them.


author: dhiman.das
body: [@DPKJ](/t5/user/viewprofilepage/user-id/690016)I appreciate it.


author: Daniel Eads
body: Hi [@dhiman.das](/t5/user/viewprofilepage/user-id/4080407) ,

I can confirm the behavior you're seeing. In the past, Opsgenie accounts were standalone, but they are now integrated with the rest of the Atlassian suite via a shared Atlassian Account. With the usage of Atlassian Accounts in OpsGenie, the fullName value is effectively overwritten by whatever name the user has set at [id.atlassian.com/manage-profile](https://id.atlassian.com/manage-profile). This is generally going to give you a good name for people who already have Atlassian accounts. However as you noticed with a random test account, that value doesn't line up. This is because the "new user" won't have a name on their Atlassian account until they verify their email address and log in to complete their account setup.

This could be a better experience - for example you might expect that fullName value to go across to the Atlassian Account to help pre-set the name. I'll raise this with our team - thank you for pointing this out and I hope the explanation is useful!

Cheers,  
Daniel \| Atlassian Support


author: dhiman.das
body: [@Daniel Eads](/t5/user/viewprofilepage/user-id/1527694)Thank you so much. I would really like to go with this "This could be a better experience - for example, you might expect that fullName value to go across to the Atlassian Account to help pre-set the name" as it will reflect the same behavior as the way UI behaves while creating a user.


Tags: cloud

user-management