Create Project settings for feature flag management

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

• Close this issue

Problem to solve

We recently introduced feature flags, feature flags permissions currently work like this: if the user has deploy permissions for all environments, he/she can turn on the feature flags.

Ww would like to control feature flags per environment , but this poses a problem for internal dogfooding as well as customer needs, since we wish for the developers to be able to turn on/off feature flags even in protected environments, but we don't want everyone to have the ability to do this.

Intended users

• Developers
• Our own delivery team

Further details

• We currently don't use protected environments for gitlab.com, but we have plans to do so. And once we do that we want to have different permissions for enabling feature flags vs running deploy job on the same environment(production).
• If the user doesn't have access to the environment, the default value of feature flag for it would be disabled on creation regardless of * scope or any other scopes.

Proposal

by maintainers, developers etc. We would like this to be more granular in the future but for MVC this is sufficient.

Permissions and Security

Documentation

Testing

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

What is the type of buyer?

Links / references