The planner role was introduced in https://gitlab.com/gitlab-org/gitlab/-/issues/482733. The search feature must be updated to support the new role. The role should give users access in search if they are able to view the data type. We can use the [permissions documentation page](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/user/permissions.md) as a reference and compare manually. ### What's currently not working The table below will be filled out to help create issues to support the work: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/189647 was used to determine which scopes are having issues. The MR added a planner role to every shared context used by the visibility specs to see what failures occurred. | Scope | Role supported? | Should role be supported? | | -- | :--: | :--: | | Code | :x: | :heavy_check_mark: **2** | | Commits | :x: | :heavy_check_mark: **2** | | Comments | :x: <br> failures on merge requests <br> failures on confidential issues | :heavy_check_mark: | | Epics | :heavy_check_mark: | :heavy_check_mark: | | Issues | :heavy_check_mark: | :heavy_check_mark: | | Work Items | :heavy_check_mark: **1** | :heavy_check_mark: | | Merge Requests | :x: | :heavy_check_mark: | | Milestones | :x: | :heavy_check_mark: | | Projects | :heavy_check_mark: | :heavy_check_mark: | | Users | :heavy_check_mark: | :heavy_check_mark: | | Wikis | :heavy_check_mark: | :heavy_check_mark: | - **1**: Issues and Epics are moving to a combined Work Items scope. When that scope is active, advanced search works as expected for planner role. Users can see both confidential and non-confidential issues - **2**: Need to confirm whether this is for public/internal projects or all visibility levels. Also the [roles & permissions documentation](https://docs.gitlab.com/user/permissions/#project-repositories) needs to be updated because it still says REPORTER role is required to view code in the footnotes