Access to specific user whereas I already have secrity levels on

[Carolina SILVA]

Hi community

I am on standard cloud.
I have a team request and need to be sure to give the correct answer.

On our projects, we used to have 2 security levels on.
- 1 restricted by default when team A creates a jira (if it's created by team B > no security levels)
- 1 that the users need to manually change when it concerns specific customers.

TODAY, we want to add some One user to access jiras we will flag / label specifically. 
BUT I don't want to impact the security levels 

As a jira access can't be be based on a custom field but only thanks to security levels, I have no clue today to positively answer to my team request.

Does someone has any clue?
Many thanks in avance.

[Jeroen Poismans]

Hello,

You can't base work item acces on a field directly, but you can base a security level on a custom field.

I understand you dont want to touch the existing levels, but  try this:

• Create a new level "Special access"
• Base it on a user custom field (Special acces user)
• Put the user in that field
• Associate that level with the work item

This way you won't impact the existing levels. I don't really see another way.

[Marc -Devoteam-]

Hi @Carolina SILVA 

Security levels are for restricting issue visibility to certain space roles, groups or users.

This is in no relation to Jira access in general.

What is your exact need, a new user needs access to Jira?

What does this user need to see in the space?

If the user needs to see issues, when security level A and or B is set the user needs to be member of the defined role or group on the security level.

[Jeroen Poismans]

The user uses the term "jira" to refer to an individual work item.

[Carolina SILVA]

a new user that will be in fact an AI to analyse jiras we'll tag
the 'user AI' need to read all the jira content to analyse it

[Marc -Devoteam-]

Hi @Carolina SILVA 

Access to issues in a space a re baed on the permission scheme and the users added to the space.

If Issue Security is used in a space, then issues in a space can be restricted to certain space roles, uger groups or individuals, there are no other options to circumvent this.

Fields on an issue don't and can't determine access.

So you need a new Security Level or if this user needs to see issues based on Team A or B, this user needs to be in the related security level.

[Arkadiusz Wroblewski]

Hello @Carolina SILVA 

A label alone will not control access in Jira Cloud. If someone should only see specific issues, that still needs to be handled through issue security / work item security. Atlassian’s own KB are clear that project permissions control access to the project, while work item security controls visibility of individual issues. 

Clean way is to add another security level and grant it either to a single user or to a user picker field value for the issues where that extra visibility is needed. 

If you want the label or a field to drive it automatically, you can use automation to set the security level. Atlassian documents that pattern too. 

restrict-access-to-certain-jira-issues-based-on-the-value-of-a-custom-field