<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">I had the same reaction: the priority field overlaps with the backlog flag.<br><br>One thing that that the backlog flag has that the priority flag doesn't is a way to nominate a bug for review of the priority via "firefox-backlog?". One could argue that every bug without an assigned priority could fall into this category but then we would want to either regularly triage recently filed bugs to set a priority on them or do a pass on all existing bugs to assign a priority making it easy to see unprioritized bugs. In general I'm not a fan of new BMO fields or whiteboard/keyword metadata that duplicate or overlap with existing metadata.<br><br>On a related note, I'm not a fan of fine-grained prioritization for low priority bugs (e.g. like the Rank field is doing). In general, it seems like either a bug is important (represented as P1, maybe P2) or it's not and so thinking about P4 vs. P5 doesn't seem useful as the reality is that neither of them are going to end up in a prioritized backlog. The only way they'll get fixed is if someone is scratching their own itch or the priority changes.<br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Another "feature" of firefox-backlog+ is that only a limited set of users can set this state. This avoids having to manually police people marking pet bugs as a priority despite the views of the module owner/peers. Maybe the existing BMO groups like canconfirm/editbugs already cover the priority field though (maybe not for bugs by the reporter?).<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Matthew<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Aug 2, 2015 at 5:53 PM, Mark Hammond <span dir="ltr"><<a href="mailto:mhammond@mozilla.com" target="_blank">mhammond@mozilla.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 1/08/2015 9:34 AM, Christopher Karlof wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I just started using the flag today to build a Desktop Sync backlog.<br>
</blockquote>
<br></span>
I've noticed bugs being changed in this way, and also the same set of bugs having the "importance" field changed (ie, a number of bugs set to P1, P2, etc).<br>
<br>
I don't understand the use of both of these. Can't the current Sync backlog be determined based on the importance? What would a P1 bug without that flag mean relative to a P5 with it?<br>
<br>
So I agree with Matt - it became clear to me very soon after the backlog flag was added that the sheer number of items marked with the flag made it useless for both filtering and prioritization, and I expect this to continue to be true for Sync. I don't mind continuing to ignore it completely, but I'd prefer to just see it die.<br>
<br>
Mark<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
<br>
-chris<br>
<br>
<br>
On Fri, Jul 31, 2015 at 2:08 PM, Matthew N.<br></span>
<<a href="mailto:MattN%2Bfirefox-dev@mozilla.com" target="_blank">MattN+firefox-dev@mozilla.com</a> <mailto:<a href="mailto:MattN%2Bfirefox-dev@mozilla.com" target="_blank">MattN+firefox-dev@mozilla.com</a>>><div><div class="h5"><br>
wrote:<br>
<br>
I just had a realization that now that we're not using a single<br>
backlog for all desktop work (we have various smaller project<br>
teams), it's not clear to me what the purpose of the firefox-backlog<br>
flag is. There are 1629 bugs set to '+'[1] which seems like a lot<br>
given that this flag was intended as a way to mark bugs that we<br>
would likely work on in approximately the next 6 months. There are<br>
bugs in there that don't seem like they are actually things we want<br>
to do.<br>
<br>
I'm curious to hear how/if people are currently using the flag and<br>
whether anyone is actually pulling bugs from there outside of bugs<br>
identified for a specific project. There are searches for good bugs<br>
from<br>
<a href="https://wiki.mozilla.org/Firefox/IterativeDevelopment#Contribute_to_Firefox_Desktop" rel="noreferrer" target="_blank">https://wiki.mozilla.org/Firefox/IterativeDevelopment#Contribute_to_Firefox_Desktop</a><br>
but I don't know if contributors are using them over bugsahoy.<br>
<br>
Perhaps the backlog is the place where the upcoming quality teams<br>
will pull from as its ideally identifying important issues in all<br>
of our components. A follow-up question would be if anyone is<br>
pruning this list?<br>
<br>
Cheers,<br>
Matthew N. (:MattN)<br>
<br>
[1]<br>
<a href="https://bugzilla.mozilla.org/buglist.cgi?f1=flagtypes.name&list_id=12437184&o1=equals&query_format=advanced&resolution=---&v1=firefox-backlog%2B&order=bug_id&limit=0" rel="noreferrer" target="_blank">https://bugzilla.mozilla.org/buglist.cgi?f1=flagtypes.name&list_id=12437184&o1=equals&query_format=advanced&resolution=---&v1=firefox-backlog%2B&order=bug_id&limit=0</a><br>
<br>
_______________________________________________<br>
firefox-dev mailing list<br></div></div>
<a href="mailto:firefox-dev@mozilla.org" target="_blank">firefox-dev@mozilla.org</a> <mailto:<a href="mailto:firefox-dev@mozilla.org" target="_blank">firefox-dev@mozilla.org</a>><br>
<a href="https://mail.mozilla.org/listinfo/firefox-dev" rel="noreferrer" target="_blank">https://mail.mozilla.org/listinfo/firefox-dev</a><span class=""><br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
firefox-dev mailing list<br>
<a href="mailto:firefox-dev@mozilla.org" target="_blank">firefox-dev@mozilla.org</a><br>
<a href="https://mail.mozilla.org/listinfo/firefox-dev" rel="noreferrer" target="_blank">https://mail.mozilla.org/listinfo/firefox-dev</a><br>
<br>
</span></blockquote>
<br>
</blockquote></div><br></div>