From fda65e2957a74508ef6ebfe84e48761d3cbcb671 Mon Sep 17 00:00:00 2001
From: Dan Jensen <djensen@gitlab.com>
Date: Thu, 27 Jan 2022 22:51:08 +0000
Subject: [PATCH] Clarify MR group label policy

For the sake of productivity metrics, MRs should have the group
label of the group that executed or coached the work, which is not
necessarily the group that owns the feature. Previously that was
not clear in the handbook, so this adds some guidance.
---
 doc/development/contributing/merge_request_workflow.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/doc/development/contributing/merge_request_workflow.md b/doc/development/contributing/merge_request_workflow.md
index cc6997e1a205..103dfb9a4006 100644
--- a/doc/development/contributing/merge_request_workflow.md
+++ b/doc/development/contributing/merge_request_workflow.md
@@ -71,6 +71,9 @@ request is as follows:
    1. The MR must include *Before* and *After* screenshots if UI changes are made.
    1. Include any steps or setup required to ensure reviewers can view the changes you've made (for example, include any information about feature flags).
 1. If you're allowed to, set a relevant milestone and [labels](issue_workflow.md).
+   MR labels should generally match the corresponding issue (if there is one).
+   The group label should reflect the group that executed or coached the work,
+   not necessarily the group that owns the feature.
 1. UI changes should use available components from the GitLab Design System,
    [Pajamas](https://design.gitlab.com/).
 1. If the MR changes CSS classes, please include the list of affected pages, which
-- 
GitLab