Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab Enterprise Edition
GitLab Enterprise Edition
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
    • Locked Files
  • Issues 3,633
    • Issues 3,633
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 229
    • Merge Requests 229
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Registry
    • Registry
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLab Enterprise EditionGitLab Enterprise Edition
  • Issues
  • #5805

Closed
Open
Opened Sep 06, 2016 by Diego Giovane Pasqualin@dpasqualin
  • Report abuse
  • New issue
Report abuse New issue

Group-level named label sets

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

In the GitLab.org group, we decide:

  • All issues now have three additional fields corresponding to the three sets.
  • All merge requests have two additional fields: Workflow and Importance.
  • All epics have one additional field: Team.

Constraint

  • The regular label field of an object can have zero, one or many labels.
  • The field associates with a named label set of an object can have zero or one label only.

Original description

I'm setting up global labels to be used on all our projects. We have labels with distinct purposes, for instance, the issue board (e.g: "In progress", "Testing"), the type of the issue (e.g: "bug", "enhancement") and the difficulty level (e.g: "noob", "hacker"). The problem is that all this different labels get mixed up in the global labels admin panel, and it becomes confusing to explain to newcomers how things work here (see image below).

Proposal

Add the ability to create groups of labels and add together labels with similar purposes.

Links / references

labels

Edited Oct 18, 2018 by Victor Wu

Related issues

Assignee
Assign to
Epic
Backlog
Milestone
Backlog
Assign milestone
Time tracking
None
Due date
No due date
8
Labels
Accepting merge requests GitLab Premium Plan UX devops:plan direction feature labels
Assign labels
  • View project labels
Reference: gitlab-org/gitlab-ee#5805