Commit c0908f49 authored by Rémy Coutable's avatar Rémy Coutable

Merge branch 'docs-update-issue_workflow' into 'master'

Update Team labels definition in the Issue Workflow documentation

See merge request gitlab-org/gitlab-ce!31811
parents 224db2f8 37b1bfca
...@@ -60,37 +60,18 @@ Subject labels are always all-lowercase. ...@@ -60,37 +60,18 @@ Subject labels are always all-lowercase.
## Team labels ## Team labels
**Important**: Most of the team labels will be soon deprecated in favor of [Group labels](#group-labels). **Important**: Most of the historical team labels (e.g. Manage, Plan etc.) are
now deprecated in favor of [Group labels](#group-labels) and [Stage labels](#stage-labels).
Team labels specify what team is responsible for this issue. Team labels specify what team is responsible for this issue.
Assigning a team label makes sure issues get the attention of the appropriate Assigning a team label makes sure issues get the attention of the appropriate
people. people.
The team labels planned for deprecation are: The current team labels are:
- ~Configure
- ~Create
- ~Defend
- ~Distribution
- ~Ecosystem
- ~Geo
- ~Gitaly
- ~Growth
- ~Manage
- ~Memory
- ~Monitor
- ~Plan
- ~Release
- ~Secure
- ~Verify
The following team labels are **true** teams per our [organization structure](https://about.gitlab.com/company/team/structure/#organizational-structure) which will remain post deprecation.
- ~Delivery - ~Delivery
- ~Documentation - ~Documentation
- ~Quality
The descriptions on the [labels page](https://gitlab.com/gitlab-org/gitlab-ce/-/labels) explain what falls under the
responsibility of each team.
Team labels are always capitalized so that they show up as the first label for Team labels are always capitalized so that they show up as the first label for
any issue. any issue.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment