diff options
| author | Mek Stittri <mstittri@gitlab.com> | 2019-06-19 11:48:49 -0700 |
|---|---|---|
| committer | Mek Stittri <mstittri@gitlab.com> | 2019-06-19 11:48:49 -0700 |
| commit | ef91d7a0d2bad8431271c57c1d3a9c800ea93a30 (patch) | |
| tree | a6b31e242a5761ca760226182cefb2e1ea521ad9 | |
| parent | 805ac20396912a7dfac60826f9b695c2c5537f8e (diff) | |
| download | gitlab-ce-severity-doc-update.tar.gz | |
Simplified language based on security feedbackseverity-doc-update
| -rw-r--r-- | doc/development/contributing/issue_workflow.md | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/development/contributing/issue_workflow.md b/doc/development/contributing/issue_workflow.md index 136cf4b72cd..3d36a7bf3b1 100644 --- a/doc/development/contributing/issue_workflow.md +++ b/doc/development/contributing/issue_workflow.md @@ -177,12 +177,12 @@ This label documents the planned timeline & urgency which is used to measure aga Severity labels help us clearly communicate the impact of a ~bug on users. There can be multiple facets of the impact. The below is a guideline. -| Label | Meaning | Functionality | Affected Customers/Users | GitLab.com Availability | Performance Degradation | -|-------|-------------------|-------------------------------------------------------|--------------------------------------------------------------------------------------------------|----------------------------------------------------|------------------------------| -| ~S1 | Blocker | Unusable feature with no workaround, user is blocked | More than 50% users affected (possible company extinction level event) | Outage, Significant impact on all of GitLab.com | | -| ~S2 | Critical Severity | Broken Feature, workaround too complex & unacceptable | Less than 50% but more than 30% of users affected including paid customers (but not apocalyptic) | Significant impact on large portions of GitLab.com | Degradation is guaranteed to occur in the near future | -| ~S3 | Major Severity | Broken feature with an acceptable workaround | Less than 30% but more than 5% of users affected including paid customers. | Limited impact on important portions of GitLab.com | Degradation is likely to occur in the near future | -| ~S4 | Low Severity | Functionality inconvenience or cosmetic issue | Less than 5% of users affected or expected to in the near future including paid customers. | Minor impact on GitLab.com | Degradation _may_ occur but it's not likely | +| Label | Meaning | Functionality | Affected Users | GitLab.com Availability | Performance Degradation | +|-------|-------------------|-------------------------------------------------------|----------------------------------|----------------------------------------------------|------------------------------| +| ~S1 | Blocker | Unusable feature with no workaround, user is blocked | Impacts 50% or more of users | Outage, Significant impact on all of GitLab.com | | +| ~S2 | Critical Severity | Broken Feature, workaround too complex & unacceptable | Impacts between 25%-50% of users | Significant impact on large portions of GitLab.com | Degradation is guaranteed to occur in the near future | +| ~S3 | Major Severity | Broken feature with an acceptable workaround | Impacts up to 25% of users | Limited impact on important portions of GitLab.com | Degradation is likely to occur in the near future | +| ~S4 | Low Severity | Functionality inconvenience or cosmetic issue | Impacts less than 5% of users | Minor impact on GitLab.com | Degradation _may_ occur but it's not likely | If a bug seems to fall between two severity labels, assign it to the higher-severity label. |