Project variables inherited from the Group, produces a 404 error when trying to view the Group variable from within the Project CI/CD Settings

For Projects that inherit Group level CI/CD variables, maintainers at the project level receive a 404 error (see below screenshot) when trying to view the variable inherited from the Group within the Project CI/CD settings. See screenshot below where the Group variables (inherited) are displayed, and have a hyperlink to to the Group where the variable is defined.

Screenshot_2023-03-03_at_2.18.47_PM

Although the user is a maintainer at the Project level, they may only be a Developer or lower at the Group level, as a result they get the 404 error as seen in the screenshot below.

Screenshot_2023-02-24_at_10.37.06_AM

Proposal: For team members at the Group-level who have a Developer role or lower, but are Maintainer or higher at the Project-level, remove the hyperlink associated with the Group inherited variable as viewed within the Project Settings, CI/CD, Variables, Group inherited variables, and perhaps even indicate in a tool tip or by hovering their mouse over the variable, that they don't have permission to view the Group variable. Screenshot below is a sample where the hyperlink is removed for a team member who doesn't have the permission to view the Group-level variable. This will make it much more user friendly from a UX perspective instead of just throwing a 404 error without any indication as to whats wrong.

Screenshot_2023-03-03_at_2.18.47_PM

Edited Jun 19, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading