Compatibility/WebCompat Priority Flags: Difference between revisions
(→webcompat tracking flag: Add image, update desc) |
m (→webcompat tracking flag: update title) |
||
| Line 1: | Line 1: | ||
== | == WebCompat Priority project flag == | ||
A Bugzilla "Webcompat Priority" project flag exists, and people can set its value to "?" to put a bug on the radar of this triage program. | A Bugzilla "Webcompat Priority" project flag exists, and people can set its value to "?" to put a bug on the radar of this triage program. | ||
Revision as of 17:37, 18 September 2020
WebCompat Priority project flag
A Bugzilla "Webcompat Priority" project flag exists, and people can set its value to "?" to put a bug on the radar of this triage program.
Webcompat Priority? bugs
Webcompat Priority? bugs are regularly triaged with the following outcomes:
1. webcompat+ is set and a priority is assigned to one of the following whiteboard tags, depending on the number of affected sites (or dupes), or how the issue affects top sites or other strategic initiatives.
- [Webcompat Priority:P1]: highest impact bugs or features for web compatibility
- [Webcompat Priority:P2]: medium impact bugs of features for web compatibility
- [Webcompat Priority:P3]: low impact bugs or features for web compatibility (but still considered important).
2. The tracking flag is left alone. The intention is to keep potentially important issues on our radar by not removing the flag — as we become aware of more site breakage it will be re-triaged and prioritized accordingly.
3. The tracking flag is cleared. This probably means the issue is not considered a compatibility issue.
Untracked queries
All bugs
| Category | Untracked | Untracked to Revisit |
| DOM | webcompat? | webcompat-revisit |
| Layout | webcompat? | webcompat-revisit |
| All | webcompat-revisit | |
| Non-Core | webcompat? |