hi Tobias, Bugzilla has many fields and teams use them in many different
ways. :) It's usually best to let the people reporting or investigating
the bugs update the bug fields.
From my experience, many (most?) teams never change a bug's "Status"
from NEW to ASSIGNED, but they still use "Assigned To". A few teams set
both, but change "Status" from NEW to ASSIGNED when the assigned
developer actually begins to work on the bug.
Despite its name, the "Target Milestone" field is usually left unset
until *after* the bug is fixed. Then "Target Milestone" is set to the
version of Firefox Nightly that was fixed (e.g. Nightly 33 is
"mozilla33"). Even if a bug fix is uplifted from Nightly 33 to, say,
Beta 31, the "Target Milestone" would stay "mozilla33", not "mozilla
31". There must have been a good reason for this at some time, but it's
hard to say for certain.. :)
chris
On 7/8/14 6:51 PM, Tobias B. Besemer wrote:
Hi!
Sorry, I have since some weeks the "can-edit" at Bugzilla and misunderstood the
"Assigned"!
I tried to help and clean up a bit Bugzilla with updating the "Target Milestone" to a Milestone that get
still developed ... and was thinking that when a bug is "Assigned To", that then the "Status" have
to be "Assigned" ...
I now realized, that this don't have to be !!!
Sorry, if I have hurt somebody with this !!!
Greets, Tobias.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
