Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

some users getting pop up of user doesn't have the set security permission

Ayush Pathak
Contributor
June 10, 2024

Some users encounter an error when attempting to create an issue, indicating that the user has not set the issue security permission. Despite being added to a specific role, the project is not linked to any issue security scheme. Why might this error occur?

image (1).png

1 answer

1 vote
Pavol Gočal
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 10, 2024

Hello @Ayush Pathak

when creating an issue, the "Security level" field is probably expected to be set. The error indicates, that the user does not have a specific permission called "Set Issue Security".

Try to verify who is allowed to set the security level in the permission scheme and check it the user has this permission.

Issue security permission.png

Ayush Pathak
Contributor
June 10, 2024

So after adding that member or group that particular member belongs to in this it will prevent the issue? but my concern is why out of sudden this issue is occurring because it wasn't previously.Screenshot 2024-06-10 at 4.34.09 PM.png

Ayush Pathak
Contributor
June 10, 2024
Pavol Gočal
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 10, 2024

If a "Security level" field is expected to be set when creating an issue (the field is available on the create screen), then the user must have the "Set issue security" permission. Adding this permission to a user or group or project role (or any other options in permission scheme) will allow user to set this field and prevent the error.

There might be several reasons why the error did not occur before:

  1. "Security level" field was not present on the create issue screen. So no need to set its value.
  2. "Set issue security" permission was modified.
  3. Different permission scheme was associated with the project.
  4. Maybe all users, that created the issue, had the permission.
  5. ...

 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events