Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 52,096
    • Issues 52,096
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,567
    • Merge requests 1,567
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #378550
Closed
Open
Issue created Oct 20, 2022 by Gina Doyle@gdoyle1️⃣Developer

Consolidate runner statuses to incorporate runner job statuses

Release notes

As part of Indicate if a runner is running a job or not (i... (#372869 - closed), there is now an indication of whether a runner is running a job. This makes the UI more cluttered and is technically a status type, but is not integrated into the status column. We have moved this to the status column to be more prominent.

Problem to solve

As part of Indicate if a runner is running a job or not (i... (#372869 - closed), there is now an indication of whether a runner is running a job. This makes the UI more cluttered and is technically a status type, but is not integrated into the status column.

I wonder if the difference between the Running and the Idle badges is enough to allow a user to quickly scan a page for runners processing jobs. Am I the only one that thinks they are not easy to spot?

While working on this I felt that only showing Running (removing the Idle badge) we would communicate a similar amount of information. Also, moving the Running badge to the status column would keep the badges together.

Intended users

  • Priyanka (Platform Engineer)

User experience goal

The user should be able to understand the status of a runner in one place.

Proposal

Move running/idle into the status column. Consider removing idle, depending on solution validation feedback.

Further details

Permissions and Security

Documentation

Availability & Testing

Available Tier

Feature Usage Metrics

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

What is the type of buyer?

Is this a cross-stage feature?

What is the competitive advantage or differentiation for this 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 Dec 09, 2022 by Gina Doyle
Assignee
Assign to
Time tracking