Improve scoped label usage for GitLab Docs planning board used by TW team
Background
-
Board used by TW team https://gitlab.com/gitlab-org/gitlab-docs/-/boards/1641178
Labels as of June 9, 2020 -
Board used by SSE team https://gitlab.com/gitlab-org/gitlab-docs/-/boards/1668857
- Begins with workflowplanning breakdown
Problem
Because we're using two different scoped labels, we often inadvertently leave docs-site labels on issues. Instead, let's try using all workflow:: labels, by creating new ones to replace the docs-site labels, but which would only be used by TW.
The existing workflow labels are all at the group level.
Proposal
Change the TW team's planning board for the GitLab Docs project (and issues themselves in gitlab-docs
project) to use the following workflow labels (so a list for each, following an initial Open list):
-
Test a new workflow:: label at the project level to determine if it acts in the 'scoped' manner with group level labels. Meaning that we can use labels at any level in the same board. (Confirmed.) -
Choose new set of labels to use. (See Proposal) -
Document what those labels mean in the context of TW team work, which may need some modification vs. their definitions at the group level. Either use the handbook, or project-level labels that contain custom definitions. -
Change labels in use, both on the board and on the issues.
Edited by Mike Lewis