summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorVictor Wu <victor@gitlab.com>2018-03-05 13:26:46 +0000
committerVictor Wu <victor@gitlab.com>2018-03-05 13:26:46 +0000
commitcb9148fc41d53475cdd31a31591aa4797a35e72b (patch)
treee6af7f9bb05862cfddde16059228b31be9cce46c
parent4a7e0821b3b3b9b7ab92b3a1c0bc94e038ce5aed (diff)
parent95cb9b229f8486a38c6a2e47db8fcc24e06c4ecd (diff)
downloadgitlab-ce-cb9148fc41d53475cdd31a31591aa4797a35e72b.tar.gz
Merge branch 'priority-changes' into 'master'
Priority labels and severity labels See merge request gitlab-org/gitlab-ce!17362
-rw-r--r--CONTRIBUTING.md11
1 files changed, 11 insertions, 0 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index b70d2da5bea..76ee6265c5c 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -196,6 +196,17 @@ release. There are two levels of priority labels:
milestone. If these issues are not done in the current release, they will
strongly be considered for the next release.
+### Severity labels (~S1, ~S2, etc.)
+
+Severity labels help us clearly communicate the impact of a ~bug on users.
+
+| Label | Meaning | Example |
+|-------|------------------------------------------|---------|
+| ~S1 | Feature broken, no workaround | Unable to create an issue |
+| ~S2 | Feature broken, workaround unacceptable | Can push commits, but only via the command line |
+| ~S3 | Feature broken, workaround acceptable | Can create merge requests only from the Merge Requests page, not through the Issue |
+| ~S4 | Cosmetic issue | Label colors are incorrect / not being displayed |
+
### Label for community contributors (~"Accepting Merge Requests")
Issues that are beneficial to our users, 'nice to haves', that we currently do