To meet the requirements of restricting visibility of some BRAVO issues to managers, others to supervisors, and keeping the remaining issues visible to all users, you need to configure anissue security schemeto define security levels and theSet Issue Securitypermission to allow users to apply these levels. These two elements are critical for implementing issue-level security in a company-managed project.
* Explanation of the Correct Answers:
* Issue security scheme (Option A):
* Anissue security schemedefines security levels that restrict who can view issues based on criteria such as users, groups, or roles. To meet the requirements, you need to create at least three security levels: one for managers, one for supervisors, and one (or none, for default visibility) for all users. The scheme is then applied to the BRAVO project to enforce these visibility rules.
* Exact Extract from Documentation:
Configure issue security schemes
Issue security schemes define security levels to restrict who can view issues. Each level specifies users, groups, or roles (e.g., managers, supervisors) who can see issues assigned to that level.
To create a scheme:
* Go toSettings > Issues > Issue security schemes.
* Create a new scheme and add security levels (e.g., "Managers Only," "Supervisors Only," "All Users").
* Assign the scheme to a project inProject settings > Issue security.Note: Security levels override theBrowse Projectspermission for restricted issues.(Source:
Atlassian Support Documentation, "Configure issue security schemes")
* Why This Fits: The issue security scheme is necessary to create security levels that restrict visibility to managers, supervisors, or all users, addressing all three requirements.
* Set Issue Security permission (Option B):
* TheSet Issue Securitypermission allows users to select a security level for an issue (via the Security Levelfield). Without this permission, users cannot assign issues to the "Managers Only" or "Supervisors Only" security levels,which is necessary to implement the restricted visibility requirements. This permission must be granted to appropriate users (e.g., project admins or specific roles) in the project's permission scheme.
* Exact Extract from Documentation:
Set Issue Security permission
TheSet Issue Securitypermission allows users to set or change the security level of an issue, determining who can view it. This permission is granted via the project's permission scheme.
To configure:
* Go toProject settings > Permissions.
* Add users, groups, or roles (e.g., Administrators) to theSet Issue Securitypermission.
Note: Without this permission, users cannot assign issues to specific security levels, even if a scheme is configured.(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Why This Fits: TheSet Issue Securitypermission is required to enable users to apply the security levels defined in the issue security scheme, ensuring that issues can be restricted to managers or supervisors as needed.
* Why Other Options Are Incorrect:
* Global permissions (Option C):
* Global permissions (e.g.,Administer Jira,Create Projects) control system-wide actions, not project-specific visibility. Issue visibility is managed by project-level permissions and security schemes, not global permissions.
* Extract from Documentation:
Global permissions control system-wide actions, such as administering Jira or sharing filters. Issue visibility is managed by project permissions and issue security schemes.
(Source: Atlassian Support Documentation, "Manage global permissions")
* Browse Projects permission (Option D):
* TheBrowse Projectspermission allows users to view issues in a project. While all users currently have this permission (since they can see all BRAVO issues), modifying it does not address the need to restrict specific issues to managers or supervisors. Issue security schemes overrideBrowse Projectsfor restricted issues.
* Extract from Documentation:
TheBrowse Projectspermission allows users to view issues in a project, but issue security levels can further restrict visibility for specific issues.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Administer Projects permission (Option E):
* TheAdminister Projectspermission allows users to manage project settings, such as components or permission schemes. While it may be needed to configure the issue security scheme or permissions, it is not directly required to meet the visibility requirements.
* Extract from Documentation:
TheAdminister Projectspermission allows managing project settings but is not required to set issue security levels or view restricted issues.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Additional Notes:
* To implement the requirements, create an issue security scheme with three levels:
* "Managers Only" (e.g., restricted to a "Managers" group).
* "Supervisors Only" (e.g., restricted to a "Supervisors" group).
* "All Users" (or no security level, allowingBrowse Projectsto apply).
* Assign the scheme to the BRAVO project and grant theSet Issue Securitypermission to users who need to assign these levels (e.g., project admins).
* The configuration requires Jira administrator privileges to create the scheme, but project admins can manage security levels within the project.
:
Atlassian Support Documentation:Configure issue security schemes
Atlassian Support Documentation:Manage permissions in Jira Cloud
Atlassian Support Documentation:Manage global permissions