It would be nice to have one (unique) account to "listen" to for bugs filed in "Mozilla Localizations -> da-DK / Danish" The current QA is (afaik) a member of the Seamonkey group ... the other groups (Firefox, Thunderbird) aren't notified when new bugs arrive in this component - that is - not until someone puts us on the CC list.... therefore - it would be good to listen to one unique account for the entire component - and then act out on those bugs that belong to ones product...
Assignee: justdave → marcia
Component: Bugzilla: Other b.m.o Issues → Bugzilla: Keywords & Components
QA Contact: myk → timeless
Soren: Did you want that email listed for the QA contact? or the assignee?
Status: NEW → ASSIGNED
If i've understood the concept of QA contact and Assignee correctly - it would be to the Assignee
Are you sure about that? Most components put the watcher account as the QA Contact so it doesn't change when somebody takes a bug. The assignee is usually somebody that deals with those types of bugs or a general "nobody" user that means nobody owns that bug.
#3 Ok .. then i've misunderstood the distinction between QA and Assignee ... My understanding of the two concepts is Assignee : the person currently assigned to deal with the bug -- if no person is assigned, a meta account holds it (that can still be listened to, if the bug gets comments before it's taken/assigned) QA: the person/account that oversees the QA process for the given component - makes sure that bugs that come into the component eventually are assigned and such... Is this a wrong/flawed understanding of the two roles/fields ?? If i've understood it correctly - i'ld still like the assignee to be firstname.lastname@example.org - and me to be placed as QA for the component - but that's perhaps another bug ;-D
(In reply to comment #4) > Assignee : the person currently assigned to deal with the bug -- if no person > is assigned, a meta account holds it (that can still be listened to, if the > bug gets comments before it's taken/assigned) > > QA: the person/account that oversees the QA process for the given component - > makes sure that bugs that come into the component eventually are assigned and > such... > > Is this a wrong/flawed understanding of the two roles/fields ?? It's not necessarily wrong, but that's not how most Components on b.m.o are set up - if the "watcher" account is set as the default assignee, then people who watch that account will stop getting mail when the bug is assigned to a real person, which sort of defeats the purpose. By having the watcher be QA contact, the watcher account will get all mail for the component regardless of who is assigned to the bug. Setting it up that way also means that multiple people can watch the default QA, if they want to. If you were the default QA, someone else who was interested in all da-dk bugs would have to watch you to get all the mail, which might mean they'd get unwanted mail.
Ok ... then set email@example.com up as QA and nobody as default assignee
Gavin, Marcia, Reed or timeless -- is it possible to get a move on regarding this bug ? there's been 10 days radio silence now ... /Søren
Status: ASSIGNED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → FIXED
Component: Bugzilla: Keywords & Components → Administration
Product: mozilla.org → bugzilla.mozilla.org
You need to log in before you can comment on or make changes to this bug.