Address UX confusion for having the same variable under different environment scopes

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

• Close this issue

Problem to solve

Right now to create a CI variable through the UI under different environment scopes, you have to create the same variable and assign it to different scopes. Which results in the screenshot below 👇

Currently the way this wildcard scope works, is each time you create a variable it's sent up with the wildcard environment scope defined.

{ "id": 13, "key": "test_var_1", "value": "test_val_1", "variable_type": "File", "protected": true, "masked": true, "environment_scope": "All", "secret_value": "test_val_1" }

Intended users

Further details

Proposal

Support multiple env scopes per variable

Permissions and Security

Documentation

Availability & Testing

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