From fc2ad91c59e9aba284a5bd7f9974bab23190d069 Mon Sep 17 00:00:00 2001 From: Mike Lewis <mlewis@gitlab.com> Date: Mon, 22 Apr 2019 04:35:37 +0000 Subject: [PATCH] Edits to example about priority labels --- doc/user/project/labels.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/user/project/labels.md b/doc/user/project/labels.md index ccec9da10b5..a06789bb940 100644 --- a/doc/user/project/labels.md +++ b/doc/user/project/labels.md @@ -28,6 +28,10 @@ Two scoped labels with the same key but a different value cannot simultaneeously apply to an issue, epic, or merge request. For example, if an issue already has `priority::3` and you apply `priority::2` to it, `priority::3` is automatically removed from the issue. +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. + ### Workflows with scoped labels **[PREMIUM]** Suppose you wanted a custom field in issues to track the platform operating system -- 2.30.9