fullName is not getting set while creating User

[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



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".

3. Here's the UI result

[DPKJ · Accepted solution]

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.

[dhiman.das]

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.

[dhiman.das]

@DPKJ 

[DPKJ]

I did tried different name, John Doe is just to give you overview.

[dhiman.das]

@DPKJAlright. Thank you. I will try with different API Key. But it's happening with every account. Even with enterprise version also.

[dhiman.das]

@DPKJI hope you have tried with a random domain apart from your test set. I really feel like something is not right.

[DPKJ]

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.

[dhiman.das]

@DPKJI appreciate it.

[Daniel Eads]

Hi @dhiman.das ,

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. 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

[dhiman.das]

@Daniel EadsThank 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.