Permissions for "Set Issue Security"

Question

Hello all,

I am currently preparing for the ACP-600 and stumbled upon the following issue.

On one page it says:

Set Issue Security is needed if an Issue Security Scheme has been applied to the project. The user also needs Browse Projects permission and Edit Issues.

On another page it says:

Users need the ‘Set Issue Security’ permission in the project's permission scheme to set the Security Level on an issue.  And, of course, they also need access to the project with the Browse Projects permission and have the permission to create issues.

Now my question is: Am I thinking too narrowly and it simply relates to different Issue Operations or is it a something else?

Thank you very much for your help!

Cheers!

Nic Brough -Adaptavist- · Answer

Yes, those are correct, but I wanted to point out that security levels are not based entirely on groups - you can use roles, individuals and fields in them as well if you want.

Florian Minterbauer · Answer

Thank you for your reply. My bad...It was already quite late in germany at that time. sorry again

I should have read through it again.
Priority should be "issue security level"

Scenario 1:
If I create an issue and want to set a security level (if the level is not set by default , then I need to be in the appropriate group/groups and have the "Create Issue Permission + Set Issue Security Permission"?

Scenario 2:
If someone created an issue and I want to set or change the security level I have to be in the appropriate group and have the "Edit Issue Permission + Set Issue Security Permission"?

Nic Brough -Adaptavist- · Answer

1. No

The issue creator can set a priority.

As I said before, the set-security only affects the security level

2. No, as per 1.

3. If an issue has a security level, only some people can see it.  Those who can see it can do whatever the rest of ythe permision sheme says they can.