diff options
Diffstat (limited to 'doc/user/project/labels.md')
| -rw-r--r-- | doc/user/project/labels.md | 45 |
1 files changed, 45 insertions, 0 deletions
diff --git a/doc/user/project/labels.md b/doc/user/project/labels.md index 18197cd860f..2cc23b14857 100644 --- a/doc/user/project/labels.md +++ b/doc/user/project/labels.md @@ -253,6 +253,35 @@ with the old labels are assigned to the new group label. The new group label has the same ID as the previous project label. +## Promote a subgroup label to the parent group + +It's not possible to directly promote a group label to the parent group. +To achieve this, use the following workaround. + +Prerequisites: + +- There must be a group that contains subgroups ("parent group"). +- There must be a subgroup in the parent group, that has a label you want to promote. +- You must have at least the Reporter role for both groups. + +To "promote" the label to the parent group: + +1. In the parent group, [create a label](#create-a-group-label) with the same name as the original + one. We recommend making it a different color so you don't mistake the two while you're doing this. +1. In the subgroup, [view its labels](#view-group-labels). You should see the two labels and where + they come from: + +  + +1. Next to the subgroup label (the old one), select **Issues**, **Merge requests**, or **Epics**. +1. Add the new label to issues, merge requests, and epics that have the old label. + To do it faster, use [bulk editing](issues/managing_issues.md#bulk-edit-issues-from-a-group). +1. In the subgroup or the parent group, [delete the label](#delete-a-group-label) that belongs to + the lower-level group. + +You should now have a label in the parent group that is named the same as the old one, and added +to the same issues, MRs, and epics. + ## Generate default project labels If a project or its parent group has no labels, you can generate a default set of project @@ -420,6 +449,22 @@ The labels higher in the list get higher priority. To learn what happens when you sort by priority or label priority, see [Sorting and ordering issue lists](issues/sorting_issue_lists.md). +## Real-time changes to labels + +> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/241538) in GitLab 14.10 with a [feature flag](../../administration/feature_flags.md) named `realtime_labels`, disabled by default. + +FLAG: +On self-managed GitLab, by default this feature is not available. To make it available, ask an +administrator to [enable the feature flag](../../administration/feature_flags.md) named `realtime_labels`. +On GitLab.com, this feature is unavailable. + +Changed labels are immediately visible to other users, without refreshing the page, on the following: + +- Epics +- Incidents +- Issues +- Merge requests + ## Troubleshooting ### Some label titles end with `_duplicate<number>` |