diff options
| author | Mek Stittri <mstittri@gitlab.com> | 2019-08-02 23:14:04 +0000 |
|---|---|---|
| committer | Mek Stittri <mstittri@gitlab.com> | 2019-08-02 23:14:04 +0000 |
| commit | cf49abccea481e5407dd5780433a72d56dc172eb (patch) | |
| tree | 88d0a9309ab8bfe9a4a75772038ccfadc2c81adf | |
| parent | 56a3334bef61f24c054b192b9c959cf1f20fd0a2 (diff) | |
| download | gitlab-ce-clarify-team-labels.tar.gz | |
Apply suggestion to doc/development/contributing/issue_workflow.mdclarify-team-labels
| -rw-r--r-- | doc/development/contributing/issue_workflow.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/contributing/issue_workflow.md b/doc/development/contributing/issue_workflow.md index fd46cb351d8..39f12e6886e 100644 --- a/doc/development/contributing/issue_workflow.md +++ b/doc/development/contributing/issue_workflow.md @@ -123,7 +123,7 @@ You can find the groups listed in the [Product Stages, Groups, and Categories][p We use the term group to map down product requirements from our product stages. As a team needs some way to collect the work their members are planning to be assigned to, we use the `~group::` labels to do so. -Normally there is a 1:1 relationship between Stage labels and Group labels. In the spirit of "Everyone can Contribute", +Normally there is a 1:1 relationship between Stage labels and Group labels. In the spirit of "Everyone can contribute", any issue can be picked up by any group, depending on current priorities. For example, an issue labeled ~"devops::create" may be picked up by the ~"group::access" group. We also use stage and group labels to help quantify our [throughput](https://about.gitlab.com/handbook/engineering/management/throughput). |