Why was changed creator on all tickets on the board to Anonymous

[Evgenii Neshumov]

Why was changed creator on all tickets on the board to Anonymous?

Hello, everyone

We noticed that on one of the boards the creator was replaced by Anonymous everywhere, while there are no changes in the history, the very first entry "Anonymous user created the Issue (date)" this happened with all tickets

Please tell me why this could happen, and how to deal with it?

[Nikola Perisic]

Welcome @Evgenii Neshumov 

• Check your filter and see if it was publicly shared
• Is the project company or team managed? If it's team managed, check your global permission Create team managed project. If it's set to Public, this means that anyone on the internet is allowed to create projects.

[Evgenii Neshumov]

We have tested these hypotheses, but we cannot understand why all the tickets on just one board have changed to anonymous

[Nikola Perisic]

Can you provide a screenshot?

[Evgenii Neshumov]

For example:

[Evgenii Neshumov]

But in mobile version Jira (iOS) creator is displayed:

[Evgenii Neshumov]

@Nikola Perisic can you give me any advice?

[Evgenii Neshumov]

Due to the lack of Creator field, our automations, which are tied through global webhooks, broke down

[Nikola Perisic]

Hi @Evgenii Neshumov , is the user claimed by a verified domain or this is a regular user that has been invited to Jira?

[Evgenii Neshumov]

What is considered a verified domain, and what is a regular user invited to Jira?

[Nikola Perisic]

For a verified domain:

When you verify a domain for your organization, you do two things:

1. Verify ownership of your company’s domain

2. Claim users' accounts with that domain.

Verifying a domain gives you two benefits:

• More control over the Atlassian accounts on your company’s domain – those accounts become managed accounts, which means you can edit, delete, or deactivate their accounts.

• The ability to apply security policies to your managed accounts – you may want to require log in with two-step verification or set up SAML single sign-on so that policies from your identity provider apply to all Atlassian accounts. You can do both by subscribing to Atlassian Guard Standard.

So a verified domain is using Atlassian Guard license to enhance the security of your users and when they are claimed they become your managed accounts.

Regular users are the users that are logging on with the username and password without any extra authentication step.

[Evgenii Neshumov]

Thanks for information

We are using verified domain

[Nikola Perisic]

Was this user removed? This is one of the reasons why this is happening.  Under the user management of your site, check if there is a user named Anonymous that was created by LDAP.

If you are on the premium, you can also check for the logs by going to admin.atlassian.com, choosing your org, security and choosing Audit log.

[Evgenii Neshumov]

No, this user is active now. All users only on this board were changed to Anonymous 

Similar behavior was noticed when setting up post mortem field is Paragraph, but in the browser it is displayed as a simple string, and in the mobile version it is Paragraph type. In the settings it is Paragraph

[Nikola Perisic]

Sadly, I don't know how it works on the iOS since I don't have the app installed.

There is an article, however it is for Data Center: https://confluence.atlassian.com/jirakb/issues-created-by-anonymous-user-in-jira-1282249581.html

Do you have access to audit log, if yes, check if you can see the user who created that issue.

[Evgenii Neshumov]

Thanks
But what's the problem with the "Post Mortem" field, in the settings it's a "Paragraph" type, but it's displayed as "Plain Text"?

[Nikola Perisic]

@Evgenii Neshumov 

I would suggest to make a separate question for that, since this was about the Anonymous users.