From 325f8590dbabee302136c669152c064aaec8093c Mon Sep 17 00:00:00 2001 From: Mark Fletcher Date: Wed, 22 May 2019 11:45:13 +0100 Subject: [PATCH] Add group label docs to Issue Workflow --- .../contributing/issue_workflow.md | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/doc/development/contributing/issue_workflow.md b/doc/development/contributing/issue_workflow.md index 0e1ab8663ed..fef94c0a4b5 100644 --- a/doc/development/contributing/issue_workflow.md +++ b/doc/development/contributing/issue_workflow.md @@ -121,6 +121,27 @@ The Stage labels are used to generate the [direction pages][direction-pages] aut [devops-stages]: https://about.gitlab.com/direction/#devops-stages [direction-pages]: https://about.gitlab.com/direction/ +## Group labels + +Group labels specify which [groups][structure-groups] the issue belongs to. + +Examples include: + +- ~"group:control" +- ~"group:editor" + +These labels should be mutually exclusive. If an issue belongs to multiple +groups, the most relevant should be used. + +Groups are nested beneath a particular stage, so only one stage label and one group label +should be applied to a single issue. You can find the groups listed in the +[Product Categories pages][product-categories]. For example, ~"group:control" and +~"group:framework" labels can be applied to issues related to the [Manage stage][manage-stage]. + +[structure-groups]: https://about.gitlab.com/company/team/structure/#groups +[product-categories]: https://about.gitlab.com/handbook/product/categories/ +[manage-stage]: https://about.gitlab.com/handbook/product/categories/#manage-stage + ## Release Scoping labels Release Scoping labels help us clearly communicate expectations of the work for the