Browse projects permission: Any logged in user vs. Jira software

[Alina Boboc]

Hello, 
I wonder what is the difference between these two options in the Browse Projects permission:

1. application access - any logged in user

2. application access - Jira Software

My current understanding is:

- "any logged in user" refers to any user logged in the Jira instance, so being member of one group associated with an application (Jira Software, Jira Core or Jira Service Management)
- Jira software refers to any user being member of a group associated with the Jira Software application (jira-software-users or similar).

So, I would expect that, with the no. 1 option, a user with application access to Jira Service Management to be able to see issues in a Jira Software project. Which doesn't happen, he can't see any issue. So, what is the difference between the two options?
Thank you.

[Dave Mathijs · Accepted solution]

Hi @Alina Boboc 

Jira Software Users can have limited access to Jira Service Management projects when they only have a JSW license.

However, users with a JSM license (Agent only) won't have access to a JSW project without a JSW license.

[Alina Boboc]

Thank you Dave for your quick reply. 

When you say "user with JSM/ JSW license", what does it mean, in terms of permissions? I think it means the user to be included in the respective group of users, associated with the JSM/ JSW application, respectively; is that correct?

Going on, it looks like, at least for the Browse Project permission, "Any logged in user" doesn't actually exist as an option; only users with application access (in the sense of belonging to the app group) may have access, unless we put a stronger restriction. 

Is this understanding correct?

Thank you :)

[Dave Mathijs]

For Server / Data Center, this means being added to a group that provides application access.

The Browse Project permission determines whether you have access to a project once you are a licensed user. And yes, there "Any logged in user" is not applicable as you need application access (i.e. a license) for that product.

[Alina Boboc]

Thank you Dave, all clear now. Have a nice day!

[Alina Boboc]

Coming back to this because I think we have to adjust a bit what we said before:
The user requires a Jira software license to be able to see the tickets in a Jira software project, in the Agile Board. Which seems normal, since the Agile Board is specific to Jira Software.

Otherwise, if the Browse project permission for the Jira Software project is granted to Any logged in user, a user with the Jira Service Management license can see the tickets in that project but not in the Agile Board.

All good now :)