In a company-managed project with issue-level security configured, theSecurity Leveldropdown field allows users to set the security level for an issue, restricting who can view it. If Andre only sees one security level instead of both, the most likely reason is that he lacks theSet Issue Securitypermission (Option C), which is required to view and select security levels in the dropdown.
* Explanation of the Correct Answer (Option C):
* TheSet Issue Securitypermission allows users to set or change the security level of an issue.
Without this permission, a user may not see all available security levels in theSecurity Level dropdown, or the field may be hidden or restricted. If Andre lacks this permission, he might only see the default security level (if set) or no options at all, depending on the configuration.
* Exact Extract from Documentation:
Set Issue Security permission
TheSet Issue Securitypermission allows users to set or change the security level of an issue, which determines who can view it. Without this permission, users cannot modify theSecurity Levelfield or may only see a subset of available levels.
To check this permission:
* Go toProject settings > Permissions.
* Verify which users, groups, or roles have theSet Issue Securitypermission.Note: The visibility of security levels in the dropdown also depends on the user's membership in groups or roles defined in the security levels.(Source: Atlassian Support Documentation,
"Configure issue security schemes")
* Why This Fits: TheSet Issue Securitypermission is directly responsible for allowing users to interact with theSecurity Levelfield. If Andre lacks this permission, he may not see both security levels, making Option C a likely reason.
* Why Other Options Are Incorrect:
* The other level is configured for different issue types (Option A):
* Issue security levels are not tied to specific issue types; they apply to all issues in a project under the issue security scheme. The configuration of security levels is project-wide, so this is not a valid reason.
* Extract from Documentation:
Issue security levels apply to all issue types in a project using the same issue security scheme. They are not restricted by issue type.
(Source: Atlassian Support Documentation, "Configure issue security schemes")
* Andre is not in a group or project role (Option B):
* While security levels may restrict visibility based on groups or project roles, the question is about Andre's ability to see security levels in the dropdown, not about viewing issues. The Set Issue Securitypermission determines whether Andre can see and select levels, not his membership in groups or roles for visibility purposes.
* Extract from Documentation:
Security levels define who can view issues (e.g., users in a group or role). TheSet Issue Securitypermission controls who can set the level, not who can view the issue.
(Source: Atlassian Support Documentation, "Configure issue security schemes")
* The other level is marked as the default (Option D):
* Marking a security level as the default ensures it is automatically applied to new issues if no level is specified. However, this does not prevent other levels from appearing in the Security Leveldropdown for users with theSet Issue Securitypermission.
* Extract from Documentation:
The default security level is applied to new issues if no level is set. All available levels are shown in the Security Leveldropdown to users with theSet Issue Securitypermission.
(Source: Atlassian Support Documentation, "Configure issue security schemes")
* Andre does not have Edit Issues permission (Option E):
* TheEdit Issuespermission allows users to modify issue fields, but theSecurity Levelfield is specifically controlled by theSet Issue Securitypermission. A user can haveEdit Issues permission but still not see security levels if they lackSet Issue Security.
* Extract from Documentation:
TheSet Issue Securitypermission is separate fromEdit Issuesand specifically controls access to theSecurity Levelfield.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Additional Notes:
* Another possible reason (not listed) could be that Andre is not in the groups or roles defined for the second security level, limiting its visibility in the dropdown. However, theSet Issue Security permission is the most direct cause listed.
* To resolve the issue, check Andre's permissions inProject settings > Permissionsand ensure he hasSet Issue Security.
:
Atlassian Support Documentation:Configure issue security schemes
Atlassian Support Documentation:Manage permissions in Jira Cloud