Users Unable to Set Specific Environments for Group Variable Environment Scope

Update

When attempting to reproduce, it looks as though the query is sound but just isn't returning data. looks like a backend issue

Summary

Users are currently unable to set Specific Environments for the Group Variable Environment Scope. Our variables documentation confirms that users should be able to select All (default) (*), a specific environment, or a wildcard environment scope.

Steps to reproduce

  1. Create a project in a top-level group with at least a premium subscription
  2. Add a project and create an environment called production
  3. Attempt to add a group variable and set the environment scope to production
  4. Observe the environment scope dropdown will show No results found.
  5. Update the environment scope to production*
  6. Observe you can select Create wildcard: production*

What is the current bug behavior?

Users are currently unable to set Specific Environments for the Group Variable Environment Scope.

What is the expected correct behavior?

Users should be able to set Specific Environments for the Group Variable Environment Scope.

Relevant logs and/or screenshots

Screenshot_2024-09-16_at_2.01.06_PM

Screenshot_2024-09-16_at_2.01.18_PM

Output of checks

This bug happens on GitLab.com

Workaround

The variable environment_scope property of Group lever variables API can be used as a workaround.

Other possible workaround that can be used is to add a * at the end of the environment name. For example use production* instead of production.

Edited by Dov Hershkovitch