Update tooltips for runner statuses
Release notes
Our runner status definitions are inconsistent across the admin, group and project areas. We will make the definitions in the tooltips more consistent across GitLab.
Problem to solve
We use different definitions in the tooltips when hovering over runner statuses in the admin, group and project areas today. It is confusing when you are navigating between 2 or 3 of those areas and see the statuses as inconsistent.
Intended users
Metrics
User experience goal
Improve the consistency of the status definitions. This should also give us a good base to add more features in the future to all 3 areas.
Proposal
-
Play button (runner is paused): Resume to accept jobs (!82702 (merged)) -
Pause button (runner is active): Pause from accepting jobs (!82702 (merged)) -
Online (runner has contacted GitLab within the last 2 hours): Runner is online; last contact was ... (!83276 (merged)) -
Offline (runner has not contacted GitLab in 2 hours+): Runner is offline; last contact was ... (!83276 (merged)) -
Never contacted (runner has never contacted GitLab): Runner has never contacted this instance (!83276 (merged)) -
Stale (Runner has not contacted for 3 months+): Runner is stale; last contact was ... (!83276 (merged)) -
Locked (Runs jobs for the currently assigned projects only): Runner is locked and runs jobs for current assigned projects only (!83588 (merged))
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.