Polish severity level facets further
This commit is contained in:
parent
ba38931d90
commit
46be2ae634
|
@ -225,24 +225,24 @@ Each issue scheduled for the current milestone should be labeled ~Deliverable
|
||||||
or ~"Stretch". Any open issue for a previous milestone should be labeled
|
or ~"Stretch". Any open issue for a previous milestone should be labeled
|
||||||
~"Next Patch Release", or otherwise rescheduled to a different milestone.
|
~"Next Patch Release", or otherwise rescheduled to a different milestone.
|
||||||
|
|
||||||
### Bug Priority labels
|
### Priority labels
|
||||||
|
|
||||||
Bug Priority labels help us define the time a ~bug fix should be completed. Priority determines how quickly the defect turnaround time must be.
|
Priority labels help us define the time a ~bug fix should be completed. Priority determines how quickly the defect turnaround time must be.
|
||||||
If there are multiple defects, the priority decides which defect has to be fixed immediately versus later.
|
If there are multiple defects, the priority decides which defect has to be fixed immediately versus later.
|
||||||
This label documents the planned timeline & urgency which is used to measure against our actual SLA on delivering ~bug fixes.
|
This label documents the planned timeline & urgency which is used to measure against our actual SLA on delivering ~bug fixes.
|
||||||
|
|
||||||
| Label | Meaning | Estimate time to fix | Guidance |
|
| Label | Meaning | Estimate time to fix |
|
||||||
|-------|-----------------|------------------------------------------------------------------|----------|
|
|-------|-----------------|------------------------------------------------------------------|
|
||||||
| ~P1 | Urgent Priority | The current release + potentially immediate hotfix to GitLab.com | |
|
| ~P1 | Urgent Priority | The current release + potentially immediate hotfix to GitLab.com |
|
||||||
| ~P2 | High Priority | The next release | |
|
| ~P2 | High Priority | The next release |
|
||||||
| ~P3 | Medium Priority | Within the next 3 releases (approx one quarter) | |
|
| ~P3 | Medium Priority | Within the next 3 releases (approx one quarter) |
|
||||||
| ~P4 | Low Priority | Anything outside the next 3 releases (approx beyond one quarter) | The issue is prominent but does not impact user workflow and a workaround is documented |
|
| ~P4 | Low Priority | Anything outside the next 3 releases (approx beyond one quarter) |
|
||||||
|
|
||||||
### Bug Severity labels
|
### Severity labels
|
||||||
|
|
||||||
Severity labels help us clearly communicate the impact of a ~bug on users.
|
Severity labels help us clearly communicate the impact of a ~bug on users.
|
||||||
|
|
||||||
| Label | Meaning | Impact of the defect | Example |
|
| Label | Meaning | Impact on Functionality | Example |
|
||||||
|-------|-------------------|-------------------------------------------------------|---------|
|
|-------|-------------------|-------------------------------------------------------|---------|
|
||||||
| ~S1 | Blocker | Outage, broken feature with no workaround | Unable to create an issue. Data corruption/loss. Security breach. |
|
| ~S1 | Blocker | Outage, broken feature with no workaround | Unable to create an issue. Data corruption/loss. Security breach. |
|
||||||
| ~S2 | Critical Severity | Broken Feature, workaround too complex & unacceptable | Can push commits, but only via the command line. |
|
| ~S2 | Critical Severity | Broken Feature, workaround too complex & unacceptable | Can push commits, but only via the command line. |
|
||||||
|
@ -251,12 +251,14 @@ Severity labels help us clearly communicate the impact of a ~bug on users.
|
||||||
|
|
||||||
#### Severity impact guidance
|
#### Severity impact guidance
|
||||||
|
|
||||||
| Label | Security Impact | Availability / Performance Impact |
|
Severity levels can be applied further depending on the facet of the impact; e.g. Affected customers, GitLab.com availability, performance and etc. The below is a guideline.
|
||||||
|-------|---------------------------------------------------------------------|--------------------------------------------------------------|
|
|
||||||
| ~S1 | >50% users impacted (possible company extinction level event) | |
|
| Severity | Affected Customers/Users | GitLab.com Availability | Performance Degradation |
|
||||||
| ~S2 | Many users or multiple paid customers impacted (but not apocalyptic)| The issue is (almost) guaranteed to occur in the near future |
|
|----------|---------------------------------------------------------------------|----------------------------------------------------|------------------------------|
|
||||||
| ~S3 | A few users or a single paid customer impacted | The issue is likely to occur in the near future |
|
| ~S1 | >50% users affected (possible company extinction level event) | Significant impact on all of GitLab.com | |
|
||||||
| ~S4 | No paid users/customer impacted, or expected impact within 30 days | The issue _may_ occur but it's not likely |
|
| ~S2 | Many users or multiple paid customers affected (but not apocalyptic)| Significant impact on large portions of GitLab.com | Degradation is guaranteed to occur in the near future |
|
||||||
|
| ~S3 | A few users or a single paid customer affected | Limited impact on important portions of GitLab.com | Degradation is likely to occur in the near future |
|
||||||
|
| ~S4 | No paid users/customer affected, or expected to in the near future | Minor impact on on GitLab.com | Degradation _may_ occur but it's not likely |
|
||||||
|
|
||||||
### Label for community contributors
|
### Label for community contributors
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue