diff options
| author | sarrahvesselov <svesselov@gitlab.com> | 2018-01-13 00:27:32 +0300 |
|---|---|---|
| committer | sarrahvesselov <svesselov@gitlab.com> | 2018-01-13 00:27:32 +0300 |
| commit | 3914f4f92f631fb7e8716e28cde1babaa794ee03 (patch) | |
| tree | 0e70786f2110d6a3f8b292f95db3a2827606b782 | |
| parent | d7b7b81d12fc79bb4e1b66ab20e32eae55a7985f (diff) | |
added examples of UX priority and severity
| -rw-r--r-- | CONTRIBUTING.md | 24 |
1 files changed, 12 insertions, 12 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 565ad94e2e6..1746552894c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -169,23 +169,23 @@ An issue should be placed on the issue board of the team that will likely handle Priority labels help us clearly communicate expectations of the work for the release. -| Label | Meaning | Product _e.g._ | Security _e.g._ | -|-------|-----------------------------------|----------------------|-----------------------------------------------| -| ~P1 | Handle immediately | Critical feature | SQL Injection, Authentication Bypass | -| ~P2 | Handle in the current release | Important feature | Cross-site Scripting, Resource exhaustion DoS | -| ~P3 | Schedule for a subsequent release | Nice-to-have feature | Tab nabbing, Path disclosure | -| ~P4 | Trivial, may not do | Suggestion | New feature, Remove dangerous protocol | +| Label | Meaning | Product _e.g._ | Security _e.g._ | UX _e.g._ | +|-------|-----------------------------------|----------------------|-----------------------------------------------|--------------------------------------------| +| ~P1 | Handle immediately | Critical feature | SQL Injection, Authentication Bypass | Major feature implemented incorrectly | +| ~P2 | Handle in the current release | Important feature | Cross-site Scripting, Resource exhaustion DoS | Minor feature implemented incorrectly | +| ~P3 | Schedule for a subsequent release | Nice-to-have feature | Tab nabbing, Path disclosure | Needs improvement, cosmetic problem | +| ~P4 | Trivial, may not do | Suggestion | New feature, Remove dangerous protocol | Suggestions, Investigate improvements | ### Severity labels (~S1, ~S2, etc.) Severity labels help us clearly communicate the impact of a ~bug on users. -| Label | Meaning | Support _e.g._ | -|-------|------------------------------------------|----------------------| -| ~S1 | Major feature broken (no workaround) | | -| ~S2 | Major feature broken (workaround exists) | | -| ~S3 | Minor feature broken | | -| ~S4 | Cosmetic problem | | +| Label | Meaning | Support _e.g._ | UX _e.g._ | +|-------|------------------------------------------|----------------------|--------------------------------------------| +| ~S1 | Major feature broken (no workaround) | | Users unable to complete a task in Merge requests, Issues, CI/CD | +| ~S2 | Major feature broken (workaround exists) | | Users unable to easily complete a task in Merge requests, Issues, CI/CD | +| ~S3 | Minor feature broken | | Users unable to complete a task in Wiki | +| ~S4 | Cosmetic problem | | UI styling does not match standards (text color, typography, etc.) | ### Label for community contributors (~"Accepting Merge Requests") |