DNS TXT Domain Verification

[Michael Arruda]

Trying to verify a domain with a TXT record, but already have a TXT record for the base domain. If I add a second TXT record will I break the first one?

Example:

JIRA Cloud Instance #1 DNS TXT Record:

example.com IN TXT atlassian-domain-verification=foo

JIRA Cloud Instance #2 DNS TXT Record:

example.com IN TXT atlassian-domain-verification=bar

Thanks

[Angélica Luz · Accepted solution]

Hello @Julian Governale,

Thank you for reaching out to the Atlassian Community!

When searching for users in the User management, the results and also sorting will be based on their Public name and not their Full name, that’s why Aleena’s information returns only when you search by the Public name (the one in round brackets).

• Update your profile and visibility settings

You can ask them to update their Public name on their Atlassian account profile to let the same as the Full name.

Kind regards,
Angélica

[Julian Governale]

Ah ok, that explains it!  Thanks @Angélica Luz  for the update.  Might need to set some standard when onboarding users to do this piece but now i know why this happens.

[Jonathan_nor]

@Angélica Luz 
I face a similar issue, but I am using Atlassian Access and have managed accounts.

For example, from Atlassian Access Directory (where only managed accounts are listed), I can look for my user typing only "John Smith" or any part of his name. I can also search him using his email: 4567@acme.com Note that his email is actually a set of number in reality.

But in the Jira user management environment, when I type "John Smith", or any part of his name, nothing shows up. I need to type part of his email "4567" to find my user. Which then shows up as "John Smith (4567@acme.com)".

Consequences for us:

1. User name must first be searched for in the Atlassian Access Directory, to copy its  email.
2. Email must then be pasted in the Jira user management environment
3. User groups can finally be edited for that specific user

Why is the search behavior so different in Jira user management and Atlassian Access Directory? That looks more like a bug then anything else to me.