I’ve got a group structure on the public GitLab instance that uses the following structure:
primary group
subgroup 1
subgroup 2
subgroup 3
I’ve already promoted the project labels to a group level, but this put the labels in each of the subgroups, where I actually want them on the primary group…
To the best of my knowledge, each group inherits the labels from it’s parent group, so what would be the best way to move these labels while maintaining label assignments in project issue?
Actually, I suspect I may be trying to do something silly here after all… If I create a label in primary group, I can’t actually use it on issues created inside subgroup 1.
So before I lose too many more brain cells, let me first ask: Is this behaviour by design?
I’ve tried the same, but the labels are not available in the projects in the subgroup1. For me this doesn’t make sense. I need to replicate the labels in the subgroups to be used by the projects.
Also, I’m not able create a issue in a project from a subgroup directly in the board of the primary group.
Yes, the flowdown of labels to from parents through sub-groups works (at least through one level of sub-groups), but still no way to promote a label from a sub-group to its parent.
After moving from Github, this was one of the things I was most excited about - but we migrated into multiple sub-groups, and now I have no way to synchronize the existing labels without some deleting and reapplying… painful.
If I go to the labels in one of my subgroups, there are three icons on the right of each label: , and a three-dot menu. If I click on the menu, there are two options:
Promote to group label
Delete
and it’s the first one you want.
If you want to synchronise your group labels automatically, you can use the labels API. There are a variety of ways to do this, personally I use a plugin to gitlab-triage to do something similar, but you might feel this is overkill in your use case.
The , have disappeared but the three-dot menu is still there with the number 1 option changed to “Edit”. When you click on the edit option, a new page is displayed with all the attributes of the label displayed, allowing you to edit them.
There is also two new text links and a “Subscribe” button:
The “Issues” and “Merge requests” links allow you to see all the issues and merge requests that have the label.
The “Subscribe” button has a hover info of “Subscribe at group level”. This occurs on labels that are already at a group level. If you click on it, it changes the button to “Unsubscribed”. Not sure what this means??
It seems like the functionality is getting closer to what’s being asked for…
just FYI: I’ve pretty much given up on GitLab… our work projects are currently being moved over to GitHub, and I’m doing much the same for my personal projects.