Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
5dc80516
Commit
5dc80516
authored
May 23, 2019
by
Rémy Coutable
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Stage labels are now scoped
Signed-off-by:
Rémy Coutable
<
remy@rymai.me
>
parent
5addbba0
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
19 additions
and
20 deletions
+19
-20
doc/development/contributing/issue_workflow.md
doc/development/contributing/issue_workflow.md
+19
-20
No files found.
doc/development/contributing/issue_workflow.md
View file @
5dc80516
...
...
@@ -92,20 +92,21 @@ Stage labels specify which [DevOps stage][devops-stages] the issue belongs to.
The current stage labels are:
-
~"devops:manage"
-
~"devops:plan"
-
~"devops:create"
-
~"devops:verify"
-
~"devops:package"
-
~"devops:release"
-
~"devops:configure"
-
~"devops:monitor"
-
~"devops:secure"
-
~"devops:defend"
-
~"devops:enablement"
These labels should be mutually exclusive. If an issue belongs to multiple
stages, the most relevant should be used.
-
~"devops::manage"
-
~"devops::plan"
-
~"devops::create"
-
~"devops::verify"
-
~"devops::package"
-
~"devops::release"
-
~"devops::configure"
-
~"devops::monitor"
-
~"devops::secure"
-
~"devops::defend"
-
~"devops::growth"
-
~"devops::enablement"
These labels are
[
scoped labels
](
../../user/project/labels.md#scoped-labels-premium
)
and thus are mutually exclusive.
They differ from the
[
Team labels
](
#team-labels
)
because teams may work on
issues outside their stage.
...
...
@@ -130,17 +131,15 @@ 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
.
These labels
are
[
scoped labels
](
../../user/project/labels.md#scoped-labels-premium
)
and thus are mutually exclusive
.
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
]
.
can be applied to a single issue. You can find the groups listed in the
[
Product Categories pages
][
product-categories
]
.
[
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
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment