Confirmed users
796
edits
Compatibility/WebCompat Priority Flags: Difference between revisions
Compatibility/WebCompat Priority Flags (view source)
Revision as of 21:15, 6 February 2020
, 6 February 2020→webcompat tracking flag: update naming
m (→webcompat? bugs: update search titles) |
m (→webcompat tracking flag: update naming) |
||
| Line 3: | Line 3: | ||
A Bugzilla webcompat tracking flag exists. Its purpose is to put interop and compat bugs on the radar, to be triaged and prioritized accordingly. | A Bugzilla webcompat tracking flag exists. Its purpose is to put interop and compat bugs on the radar, to be triaged and prioritized accordingly. | ||
==== | ==== Webcompat Priority? bugs ==== | ||
[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=webcompat%3F&sharer_id=389500&list_id=14538489 | [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=webcompat%3F&sharer_id=389500&list_id=14538489 Webcompat Priority? ] bugs are regularly triaged with the following outcomes: | ||
1. [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=webcompat%2B 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. | 1. [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=webcompat%2B 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. | ||