As glob noted upthread, the NEW/ASSIGNED distinction is sometimes used
by people when they are the assignee. There is only a lack of difference
when the assignee is "nob...@mozilla.org". That doesn't warrant
abolishing the status (although we could arguably ask bmo folks to make
the "reset the assignee to default" also set the status to "new" if the
status was previously "assigned")
~ Gijs
On 09/07/2014 16:45, Milan Sreckovic wrote:
What’s the purpose of the “ASSIGNED" status? If we’re saying that this status
can be computed from Assigned To field (being set to nobody or something else), then
why do we still have it? If it isn’t equivalent, then we may be losing some
information if we reset it back to New.
--
- Milan
On Jul 9, 2014, at 11:27 , Daniel Holbert <dholb...@mozilla.com> 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
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
