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
817c2c44
Commit
817c2c44
authored
May 20, 2019
by
Jan Provaznik
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add a note about nested scopes matching
parent
82c4a99c
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
0 deletions
+6
-0
doc/user/project/labels.md
doc/user/project/labels.md
+6
-0
No files found.
doc/user/project/labels.md
View file @
817c2c44
...
...
@@ -32,6 +32,12 @@ An issue, epic, or merge request cannot have two scoped labels with the same key
For example, if an issue is already labeled
`priority::3`
and you apply the label
`priority::2`
to it,
`priority::3`
is automatically removed.
NOTE:
**Note:**
In the case where labels have multiple sets of
`::`
, the longest path is used
for mutual exclusivity check. For example, for label
`some::key::value`
we
would check for exclusivity on
`some::key::`
level instead of
`some::`
- this
allows finer grained organization.
### Workflows with scoped labels **[PREMIUM]**
Suppose you wanted a custom field in issues to track the platform operating system
...
...
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