On 09/07/2014 16:27, Daniel Holbert wrote:
On 07/09/2014 08:16 AM, Gijs Kruitbosch wrote:
On 09/07/2014 16:00, Tobias B. Besemer wrote:
My next run would be "Status = Assigned" & "Assigned To =
nob...@mozilla.org" ...
Tobias.
Please don't mass change the target milestone flag on bugs (definitely
not manually). Same goes for the assignee field.
~ Gijs
To be clear, I don't think he's planning on mass-changing the *assignee*
field -- rather, it sounds like his next plan was to reset Status to
"NEW", for bugs that are ASSIGNED but have no assignee.
That seems like a reasonable sort of change to me. Of course, any
mass-change in Bugzilla could have unintended consequences or step on
toes in some obscure component with its own rules; but AFAIK, this
particular change seems likely to just be a change to better-reflect
reality.
(I'm not sure how much value it adds, but I don't see it doing much harm.)
~Daniel
Either change should be done through a mass change that doesn't cause
bugmail, so not by a casual contributor without the right bmo
privileges. Otherwise we're just wasting (a) a lot of their and our
(collective) time, and (b) don't gain very much. :-)
I'm also not sure about whether changing the target milestone of
unclosed bugs (I'm hoping these are all unclosed bugs...) doesn't end up
losing us stuff we care about. Even if that isn't the case in our
primary products/components, we have rather a lot of them.
If people want to contribute to the state of our bugtracking db, using
mozregression with bugs that have regressionwindow-wanted set, or
creating testcases for bugs that are filed, or triaging stuff from
Fx::Untriaged into a better component (provided they have a good idea of
what component stuff goes in) is likely to be more helpful...
~ Gijs
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
