diff options
| author | Mark Fletcher <mark@gitlab.com> | 2019-05-22 11:45:13 +0100 |
|---|---|---|
| committer | Mark Fletcher <mark@gitlab.com> | 2019-05-22 11:55:07 +0100 |
| commit | 325f8590dbabee302136c669152c064aaec8093c (patch) | |
| tree | 55c9d38de3cc36130e59fcfd0663eb6d5003e64c | |
| parent | 3fc64f38e7fbebe917c2a82156ccf2612d65e9e0 (diff) | |
| download | gitlab-ce-325f8590dbabee302136c669152c064aaec8093c.tar.gz | |
Add group label docs to Issue Workflow
| -rw-r--r-- | doc/development/contributing/issue_workflow.md | 21 |
1 files changed, 21 insertions, 0 deletions
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 |