Replace the runner 'active' state with a new filter 'paused'

Release notes

In the Runner Admin view, we are allowing users to filter by Active, even though we don't display it as a status anymore in the status column. To solve the inconsistency, we will remove active as status filter and replace it with a new filter Paused, which can be set to Yes or No.

Problem to solve

This came up as a followup from !73680 (comment 722723867).

We still allow for users to filter by active even though it is not a status that we reflect in the status column for the runner table. That is inconsistent with the rest of the statuses that we list there and in the status column.

Intended users

Metrics

User experience goal

Have a single, consistent way of differentiating statuses from configurations of the runner.

Proposal

We should remove the active value from the status filter group, and replace it with a new filter Paused with values Yes or No. These will correlate with the pause/play button for each runner.

We should also remove the paused badge in the status column, we can rely on the pause/play button to communicate its active/inactive states.

Further details

Permissions and Security

Documentation

Availability & Testing

Available Tier

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Edited by Gina Thisse