I used the uiwanted keyword in Firefox front-end components to indicate that a bug needs UX input before it can move forward, without explicitly flagging a particular UX person because the bug has a low priority. It's valuable meta data even if nobody monitors all uiwanted bugs. How do you suggest we support that use case going forward? There's the whiteboard but that seems like a step backwards.
TIA, Dao Am Fr., 26. Apr. 2019 um 01:52 Uhr schrieb Emma Humphries <e...@mozilla.com >: > Typo: s/uineeded/uiwanted/gi > > On Thu, Apr 25, 2019 at 4:50 PM Emma Humphries <e...@mozilla.com> wrote: > >> Previously teams and other contributors have used the uineeded keyword in >> Bugzilla to indicate if the UX team’s expertise was needed. >> >> However, that keyword, with a couple of exceptions, is not currently >> monitored by that team. >> >> In order to prevent misunderstandings, I will be disabling the uineeded >> keyword in Bugzilla. It will appear in bugs that have it until it is >> removed so you may clean up backlogs, but it will no longer be able to be >> set for new bugs. >> >> If you are working with a UX team member who is monitoring Bugzilla bugs >> (DevTools and Activity Stream) then please use needinfo to call out bugs to >> them. >> >> Otherwise, please work with the UX managers (Tif, Markus, and Anthony >> who all reviewed this) to ask about getting UX resources to help with >> your project. >> >> The relevant BMO bug for this is: >> https://bugzilla.mozilla.org/show_bug.cgi?id=1541690 >> >> In May I will be working with the UX managers to investigate a >> replacement UX triage for Bugzilla. >> >> -- Emma >> >> >> >> >> >> _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
