Allow non-member groups to be configured in deployment approvals

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

• Close this issue

Release notes

Problem to solve

As a compliance manager, I want to require 1 approval from members of Group A before a deployment can be started for a specific (protected) environment, but for safety reasons we don't allow groups to be added to projects as members.

I want a free-type input at the deployment approval setup where I can provide a group name, and GitLab will take it from me. This is already possible with Merge Request approvals.

Proposal

Intended users

• Rachel (Release Manager)
• Dakota (Application Development Director)
• Cameron (Compliance Manager)

Feature Usage Metrics

No. We already measure protected environment settings.

Does this feature require an audit event?

Yes. It already exists protected_environment_approval_rule_*