Description

Managing label sets

• Define/manage sets of labels at the group level.
• So at the group level, you can have distinct sets of labels.
• In the first iteration, there isn't any subgroup support. So for a given group, you have labels at that group level, and you can create sets of labels for that group only. You can't create a set that sucks in labels from a parent/ancestor group.

Configuring label set usage

• At the group level, you define that all issues/merge requests/epics need to use certain label sets defined.

Example

In the GitLab.org group, there are these label sets with these labels:

• Label set called Workflow:
  • The labels in this set are: In Dev, In Review
• Label set called Team
  • The labels in this set are: Discussion, Platform, Distribution
• Label set called Importance
  • The labels in this set are: Deliverable, Stretch
• Label set called Epic Review
  • The labels in this set are: UX Pending Review, UX Approved, BE Pending Review, BE Approved, FE Pending Review, FE Approved

In the GitLab.org group, you decide that:

• For every issue, it requires to have these distinct label fields:

  • Workflow, Team, Importance, Any Label.

• For every epic, it requires to have these distinct label fields:

  • Epic Review, Any Label

e.g.

Original description