Re: Tooling and reporting changes

That's arewetriagedyet.net, not. org. Sorry for the confusion. -- Emma On Thu, Apr 30, 2020 at 6:14 PM Emma Humphries wrote: > Hi, thank you all for your questions and comments on the changes to the > triage process starting this Monday with the next merge. I want to > acknowledge that we're a

Re: Tooling and reporting changes

That should be triaged as severity = n/a, and I'll make sure the triage definition is clear that if the severity is n/a then the status_firefoxNN flags do not need to be set. Thanks for calling it out! -- Emma On Fri, May 1, 2020 at 7:39 AM Kartikaya Gupta wrote: > With this new triage query,

Re: Tooling and reporting changes

With this new triage query, a bug like https://bugzilla.mozilla.org/show_bug.cgi?id=1633584 is considered untriaged, because it doesn't have any of the status-firefoxXX flags set. However it's an "enhancement" type bug and so those flags don't really make much sense to be setting. Is this intention

[IMPORTANT] Submit your PI Requests for Firefox 78 QA feature testing by May 8

Similar to what QA did for previous Firefox feature testing prioritization , we would like to do the same for Fx78. In order to help with the process, please *submit your PI-Request