Browse Source

Merge pull request #18623 from kittykat/triage-process

README: link to wiki for issue triage process and labels
Kat Gerasimova 9 months ago committed by GitHub
No known key found for this signature in database
  1. 83


@ -401,83 +401,6 @@ For a developer guide, see the [translating dev doc](docs/
Triaging issues
We strive to completely cover all applicable issues with these core labels:
1. __Type__ — Every issue is assigned a type:
* __[T-Defect](
Bugs, crashes, hangs, vulnerabilities, or other reported problems
* __[T-Enhancement](
New features, changes in functionality, performance boosts, user-facing
* __[T-Task](
Refactoring, enabling or disabling functionality, other engineering tasks
* __[T-Other](
Questions, user support, anything else
2. __Severity__ — All issues labeled `T-Defect` are also assigned a severity:
* __[S-Critical](
Prevents work, causes data loss, affects many users, and/or has no
* __[S-Major](
Severely degrades major functionality or product features, with no
satisfactory workaround
* __[S-Minor](
Impairs non-critical functionality, or suitable workarounds exist
* __[S-Tolerable](
Purely cosmetic or low / no impact to users
3. __Prevalence__ — All issues labeled `T-Defect` are also assigned a prevalence:
* __[P-High]( Affects most users regularly or impacts most users' first experience (e.g. registration)
* __[P-Medium]( Affects some users regularly or most users rarely
* __[P-Low]( Most users are unlikely to come across this or it is a corner case
This label may also be used for other types of issues.
4. __Area__ — Most issues are assigned one or several "areas" using one of the
many `A-` prefixed labels, e.g. `A-Composer` or `A-Spaces`. Each area label
maps to a group of features or portion of the UI surface in the app.
The Priority label is now deprecated. Defects will now be classed based on their severity and prevalence:
| Labels | Equivalent priority | What it means |
| ----------- | ----------- | ----------- |
| S‑Critical and P‑High<br />S‑Critical and P‑Medium<br />S‑Major and P‑High | P1 | These issues should be worked on in this sprint or next sprint. If the backlog of issues is too long, we should reevaluate why the bugs are not caught earlier. |
| S‑Critical and P‑Low<br />S‑Major and P‑Medium<br />S‑Minor and P‑High | P2 | When all the highest priority bugs are done, this is the next set to tackle. Ideally we should be fixing a few issues from this group every week. |
| S‑Major and P‑Low<br />S‑Minor and P‑Medium<br />S‑Tolerable and P‑High | P3 | These issues are wishful thinking for now. We hope to get to them one day, but they are low priority. There are likely to be some good new contributor issues in here. |
| S‑Minor and P‑Low<br />S‑Tolerable&nbsp;and&nbsp;P‑Medium<br />S‑Minor and P‑Low | P4 and P5 | These issues are unlikely to be actively looked at by the webapp team, but may be picked up by community. |
### Other common labels
We have a handful of other labels which are added on an as-needed basis, and not expected to be exhaustive:
* __Exceptions__ — Special flags for issues and pull requests:
* __[X-Needs-Info](
This issue is blocked pending further information from the reporter
* __[X-Regression](
Denotes things breaking which previously worked
* __[X-Release-Blocker](
Issues which must be resolved before making a release
* __[Easy]( / __[Help
Wanted]( —
Well-defined issues which are suitable for folks new to the codebase
* __[A11y]( /
__[Meta]( /
__[I18n]( /
__[Privacy]( /
__[Security]( —
Issues which fall under these conceptual themes (which apply to many software
projects and are not specific to Element)
* __[Sponsored]( —
Used internally by Element to denote issues with external funding
### Ad hoc labels (`Z-`)
We have reserved the `Z-` prefix for ad hoc labels.
Any member of the core team is welcome to create labels beginning with `Z-` for
any purpose, such as tracking personal areas of interest or providing a common
way to label cross-repo initiatives. The prefix avoids interference with the
project's main labels.
Issues are triaged by community members and the Web App Team, following the [triage process](
We use [issue labels]( to sort all incoming issues.