From 817c2c44f528fda8b68a98ada04b9741a3c9e3d1 Mon Sep 17 00:00:00 2001 From: Jan Provaznik Date: Mon, 20 May 2019 10:18:08 +0200 Subject: Add a note about nested scopes matching --- doc/user/project/labels.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/doc/user/project/labels.md b/doc/user/project/labels.md index ac91cd4ea98..8869d85bbe0 100644 --- a/doc/user/project/labels.md +++ b/doc/user/project/labels.md @@ -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 -- cgit v1.2.1