<!-- Implementation issues are used break-up a large piece of work into small, discrete tasks that can move independently through the build workflow steps. They're typically used to populate a Feature Epic. Once created, an implementation issue is usually refined in order to populate and review the implementation plan and weight. Example workflow: https://about.gitlab.com/handbook/engineering/development/threat-management/planning/diagram.html#plan --> ## Release notes The Admin Area > Runners view has been re-designed. In addition to new layout options, the re-design enables future improvements for runner fleet management from the Admin Area > Runners view. The key new features available in this redesign are as follows: - Filter the Runner view by runner type tabs. - Fix the filter, so the view now correctly displays non-connected runners. ## Why are we doing this work The Admin Area > Runners view needs to be re-designed to allow for more data to be added. More details in the design issue: https://gitlab.com/gitlab-org/gitlab/-/issues/299509/ ## Relevant links - [Design Issue](https://gitlab.com/gitlab-org/gitlab/-/issues/340324/) ## Non-functional requirements <!-- Add details for required items and delete others. --> To be completed - [x] Documentation: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/74165 ## Implementation plan - [x] Move register runner information to a dropdown https://gitlab.com/gitlab-org/gitlab/-/merge_requests/72529 - [x] Replace registration token in registration modal ​https://gitlab.com/gitlab-org/gitlab/-/merge_requests/72705 - [x] Fix filtering of "Not connected" runners https://gitlab.com/gitlab-org/gitlab/-/merge_requests/73292 - [x] Remove runners' table jobs and projects columns https://gitlab.com/gitlab-org/gitlab/-/merge_requests/73472 - [x] Runner status cannot be "paused" https://gitlab.com/gitlab-org/gitlab/-/merge_requests/73530 - [x] Filter runner type via tabs https://gitlab.com/gitlab-org/gitlab/-/merge_requests/73680