Group runners not visible in subgroup settings but visible in subgroup projects

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

  • Close this issue

Summary

Group runners from the parent group are not visible when viewing the subgroup's CI/CD runners settings page, but they ARE visible and accessible when viewing the CI/CD settings of projects within that subgroup.

Steps to reproduce

  1. Create a group hierarchy: ParentGroup -> Subgroup -> Project
  2. Create/register a group runner at the ParentGroup level
  3. Navigate to ParentGroup/Subgroup/-/settings/ci_cd (subgroup CI/CD settings)
  4. Observe the runners list - the parent group runner is NOT shown
  5. Navigate to ParentGroup/Subgroup/Project/-/settings/ci_cd (project CI/CD settings)
  6. Observe the runners list - the parent group runner IS shown and available

Current behavior

  • Parent group runners are not visible in the subgroup's CI/CD runners settings page
  • This creates an inconsistent user experience where runners appear to be unavailable at the subgroup level
  • However, the runners ARE actually inherited and available to projects within the subgroup

Expected behavior

  • Parent group runners should be visible in the subgroup's CI/CD runners settings page
  • The visibility should be consistent between the subgroup level and project level
  • Users should be able to see all available runners (both subgroup and inherited parent group runners) at the subgroup settings level

Relevant information

  • This affects the UI/UX consistency
  • The runners ARE functionally inherited (they work in projects)
  • The issue is purely about visibility in the subgroup settings page
Edited Feb 21, 2026 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading