Move compliance framework project labels from Ultimate to Premium
Problem to solve
We introduced compliance framework project labels in %12.10, but have since introduced additional features that conflict with the pricing tier of this feature. For example, we want to leverage these project labels to allow administrators to limit the scope of instance-level settings to specific compliance framework-labeled projects.
Currently, organizations must be in Ultimate
to label a project with a specific compliance framework, but have access to these labels as a refinement mechanism in the admin area
in Premium
. To reconcile this difference and to move the feature down quickly, we should move this new feature (compliance framework labels for projects) from Ultimate
to Premium
.
Intended users
User experience goal
A Premium
or above GitLab customer can apply a compliance framework label to their projects and reduce the scope of inheritance on instance-level settings based on these labels.
Proposal
Move compliance framework project labels from Ultimate
to Premium
Further details
This feature was recently launched in %12.10 and should be more broadly available in Premium
both to satisfy customer needs and reconcile the discrepancy between the two mentioned features.