Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #2312

Closed
Open
Created Dec 20, 2012 by Administrator@rootOwner

label groups

Created by: tkluck

I'm looking into migrating from Trac to Gitlab for the Sage open source project [1]. One thing that Gitlab currently lacks is being able to categorize issues by combo-boxes. The "labels" feature doesn't quite cut it, because in some cases, you want to force reporters to make a choice.

This led to my trying to implement such a feature, see this pull request [2]. Riyad thought my implementation too complex, and I think he is right. I've thought about this some more in the mean time. I think that my needs would be served by supporting something that I would call "label groups". Riyad suggested something similar.

I would imagine something like the following: Gitlab automatically treats labels of the form a:b as belonging to a group called "a". They are shown grouped in the label overview. The project administrator can use a checkbox next to each group to mark the group as "mandatory" (which means that any issue must have at least one of these labels) and/or "mutually exclusive" (meaning that every issue has at most one of these labels).

Then in the issue overview, labels that are both "mandatory" and "mutually exclusive" are automatically shown as a combobox.

I can implement this, if you think there's a reasonable chance you would accept such a pull request. I'm looking forward to any feedback you may have.

[1] www.sagemath.org [2] https://github.com/gitlabhq/gitlabhq/pull/2154

Assignee
Assign to
Time tracking