Again, can we please re-enable the uiwanted keyword so I can continue to
use it until the replacement is implemented? The suggested interim
replacement, needinfo, does not fit.
It doesn't seem that there's much won by overeagerly disabling the keyword
as the queue (that nobody has been looking at
Hi Dão,
Thank you for calling out that use case. This week I met with one of the UX
managers to plan a replacement for the keyword. The goal here is to have a
work queue that UX can triage and is visible to all the stakeholders.
I'll report on that soon.
-- Emma
On Wed, May 15, 2019 at 3:41 AM
After reading the bug, it seems that this use case was just completely
missed, and only UX people who barely use bugzilla were consulted.
Therefore I'd like to ask that we re-enable this keyword until we have a
proper replacement.
Thanks,
Dao
Am Mi., 15. Mai 2019 um 12:28 Uhr schrieb Dão Gottwald
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
Typo: s/uineeded/uiwanted/gi
On Thu, Apr 25, 2019 at 4:50 PM Emma Humphries 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
>
5 matches
Mail list logo
