<!-- The first section "Release notes" is required if you want to have your release post blog MR auto generated. Currently in BETA, details on the **release post item generator** can be found in the handbook: https://about.gitlab.com/handbook/marketing/blog/release-posts/#release-post-item-generator and this video: https://www.youtube.com/watch?v=rfn9ebgTwKg. The next four sections: "Problem to solve", "Intended users", "User experience goal", and "Proposal", are strongly recommended in your first draft, while the rest of the sections can be filled out during the problem validation or breakdown phase. However, keep in mind that providing complete and relevant information early helps our product team validate the problem and start working on a solution. --> This is a spin-off of https://gitlab.com/gitlab-org/gitlab/-/issues/19819 and https://gitlab.com/gitlab-org/gitlab/-/issues/334686#note_620693062 ### Release notes "When users of the group runner UI visit their runners' page, they can see the runners that they administer, but this is not a full picture of the runners that are available to them. This change enables users to see all the runners they can use, that are made available to them at different levels: shared runners, and runner from parents groups, along with runners they administer." In other words: Admins can **manage** all the runners under them, Devs can **see** all the runners available to them. ### Problem to solve There are two types of relationships between a "scope" (a project or group) with the runners they use: 1. The runners that are "owned" by a group: - all the runners in this group plus, - all the runners owned by subgroups. 2. The runners that can be used by jobs of a group: - which can be all runners in this group plus, - all the runners in descendant groups and projects plus, - all the group runners owned by ancestor groups plus, - all shared/instance runners. When visiting the runners' admin page, both relationships could be represented by the UI to help users understand which are the resources they can manage and use. See comment https://gitlab.com/gitlab-org/gitlab/-/issues/337838#note_811564755 for more details ### Intended users * [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead) * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) * [Sidney (Systems Administrator)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator) ### User experience goal The user should be able to see all the runners at their disposal as well as seeing why a given runner is a available to them. ### Proposal **Design proposal** https://www.loom.com/share/99df714ea3af4d48902cd220dfd1c851 * Print all runners available to you to run jobs (runners in this group, all runners owned by ancestor groups, all instance runners). These would be listed in the *All* tab as well as the individual `Instance`, `Group`, and `Project` tabs, depending on what types of runners they are. * Runners that you are not the owner of should have *no* actions available and *no* links to see details of those runners. * :bulb: I wanted to make it clear where these runners are coming from, so I proposed adding a switch to the filter bar that allows you to see `only runners you manage` vs `all runners available to me`. If we choose to go this route, I'll need to make sure we get the ~"UI text" reviewed. * **Note:** Once we add [owners](https://gitlab.com/gitlab-org/gitlab/-/issues/355766), this will become MUCH more clear where those runners were registered. **Example of how this looks as a group owner:** | all runners printed | instance runners available to me | only show me the runners I managed | | ------ | ------ | ------ | |  |  |  | **Example of how this looks as an admin:** I can edit and click on all runners. I'd recommend we'd remove the toggle to show/hide `runners available to me` in this case as technically, it wouldn't do anything to the list. **Previous technical proposal (might need edits)** The feature can be done by adding a new filter parameter in the `membership` fields of the GraphQL  Such filter can be named `ALL`, `ANCESTORS`, or other... that are added to the groups listing https://gitlab.com/gitlab-org/gitlab/-/merge_requests/65673. ### Further details <!-- Include use cases, benefits, goals, or any other details that will help us understand the problem better. --> ### Permissions and Security As users that are not administrators of a certain runner will be able to see it listed, some actions will not be available to them: - They will not be able to edit, pause/activate, delete the runners that are in higher scopes, unless they have permissions over such higher scopes. :point_up: As an additional benefit of this change, the Group Runners page can become available to all users that are members of the group -> They will see the list of runners without having administration capabilites. ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/workflow.html#for-a-product-change * Add all known Documentation Requirements in this section. See https://docs.gitlab.com/ee/development/documentation/workflow.html * If this feature requires changing permissions, update the permissions document. See https://docs.gitlab.com/ee/user/permissions.html --> ### Availability & Testing <!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier. What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance. * Unit test changes * Integration test changes * End-to-end test change See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning --> ### Available Tier <!-- This section should be used for setting the appropriate tier that this feature will belong to. Pricing can be found here: https://about.gitlab.com/pricing/ * Free * Premium/Silver * Ultimate/Gold --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. Create tracking issue using the the Snowplow event tracking template. See https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Snowplow%20event%20tracking.md --> ### What is the type of buyer? <!-- What is the buyer persona for this feature? See https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/buyer-persona/ In which enterprise tier should this feature go? See https://about.gitlab.com/handbook/product/pricing/#three-tiers --> ### Is this a cross-stage feature? <!-- Communicate if this change will affect multiple Stage Groups or product areas. We recommend always start with the assumption that a feature request will have an impact into another Group. Loop in the most relevant PM and Product Designer from that Group to provide strategic support to help align the Group's broader plan and vision, as well as to avoid UX and technical debt. https://about.gitlab.com/handbook/product/#cross-stage-features --> ### Links / references **Future iteration** Additionally, users should be able to select this option when visiting the Group Runner UI:  <!-- Label reminders - you should have one of each of the following labels. Use the following resources to find the appropriate labels: - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->