nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira Licenes details

DJM

Hi,

i would like to know details regarding the Jira Licenses and was going through some of document and in the document it is mention that any user added to group Jira users is will be treated as count for license which is correct.And also it mention Unlimited 'anonymous users' are permitted on all licenses. so my question is any user if not part of Jira users group so where is the question of then access Jira when his/her id is not part of this group Jira Users.In short want to know what is this Unlimited 'anonymous users' are permitted on all licenses. how anonymous user will access Jira when it is not part of Jira core user as per defination

Thanks

DJM

Accepted answers

All comments

Alexey Matveev

You can permit the anonymous user in the project permission scheme. It means that the user will be able to see the project and do actions even without logging. But all actions will be taken from an anonymous user. You will not know who exactly the user was.

DJM

Hi,

will not user should get inherited from global setting(permissions) and under what case anyone will add anonymous user in project when it is not reflected in global setting.

so is this need for automation or is it service account in short why anyone will add such user on project scheme and for what purpose this is will be interesting to know

Thanks

DJM

Alexey Matveev

the anonymous user is a built-in "user". You do not need to add it to global permissions. the anonymous user means that the user does not log in to Jira. If you want to automate functions, you can distinguish between logged-in user and not logged-in.

I never used anonymous user. The problem is that you will never know who exactly performed an acion in Jira.

Nic Brough -Adaptavist-

Anonymous access can be useful - imagine you have some software and you want to be open about the current list of improvements and bugs. You would open the bug and improvement tracking project to the world to see without having to log in. For example jira.atlassian.com is tracking them across the whole Atlassian suite.

But as Alexey says, you really don't want to grant it for much more than "Browse project". Anything a user can do that writes data really should be trackable, so you would never allow anonymous edit, create, comment and so-on, as you cannot know who the person making the changes is.

(One minor exception - I've recently set up a system where the owners want people without accounts to go through a request process. We allow anonymous users to create issues in a single project which asks them for their name and business unit to get the access process started)