The Customer Relations team can see two projects (indicating they haveBrowse Projectspermission) but not the project boards, and they want to share advanced searches (filters) with other project members. The permission required to share filters without granting excessive access is theShare dashboards and filters global permission (Option B).
* Explanation of the Correct Answer (Option B):
* TheShare dashboards and filtersglobal permission allows users to share filters and dashboards with other users, groups, or roles. This permission is necessary for the team to make their advanced searches visible to other project members. It is a targeted permission that does not grant additional administrative or project-level access.
* Exact Extract from Documentation:
Share dashboards and filters permission
TheShare dashboards and filtersglobal permission allows users to share filters and dashboards with other users, groups, projects, or the entire organization.
To grant this permission:
* Go toSettings > System > Global permissions.
* Add a user, group, or role to theShare dashboards and filterspermission.Note: This permission is required to make filters or dashboards accessible to others, but it does not grant access to view issues or manage boards.(Source: Atlassian Support Documentation,
"Manage global permissions")
* Why This Fits: TheShare dashboards and filterspermission directly enables the team to share their advanced searches (filters) with other project members without granting unnecessary privileges, making Option B the correct choice.
* Why Other Options Are Incorrect:
* Browse Projects (Option A):
* TheBrowse Projectspermission allows users to view issues in a project. Since the team can already see two projects, they likely have this permission. It does not control the ability to share filters or access project boards.
* Extract from Documentation:
TheBrowse Projectspermission allows users to view issues and projects. It does not include sharing filters or managing boards.
(Source: Atlassian Support Documentation, "Manage project permissions")
* Board administrator (Option C):
* TheBoard administratorrole (orManage Sprintspermission for company-managed projects) allows users to manage boards, including viewing and editing them. While this would allow the team to see project boards, it grants excessive access (e.g., modifying sprints) and does not address sharing filters.
* Extract from Documentation:
Board administrators can manage board settings and sprints. This role is not required to share filters or dashboards.
(Source: Atlassian Support Documentation, "Manage boards in Jira Cloud")
* Administer Jira (Option D):
* TheAdminister Jirapermission (Jira administrator role) grants full access to global settings, including user management, schemes, and permissions. This is far too much access for the team's needs, which are limited to sharing filters.
* Extract from Documentation:
TheAdminister Jirapermission grants access to all global settings. It is not needed for sharing filters or viewing boards.
(Source: Atlassian Support Documentation, "Manage global permissions")
* Additional Notes:
* The team's inability to see project boards likely stems from lacking theView Development Tools orManage Sprintspermission, or not being board administrators. However, the question focuses on sharing filters, soShare dashboards and filtersis the relevant permission.
* The permission can be granted to the team via a group inSettings > System > Global permissions.
:
Atlassian Support Documentation:Manage global permissions
Atlassian Support Documentation:Manage project permissions
Atlassian Support Documentation:Manage boards in Jira Cloud
Atlassian Support Documentation:Manage filters in Jira Cloud