Re: Done: Planned changes to bugzilla step 2

Hb schrieb:
>> 1. Step
>> Change the default account
>> from  [email protected]  "Xaraya QA Group"
>> to    [email protected]     "Nobody; OK to take it and work on it"
>> 
>> This will reflect the current situation on most bugs best. This setting is usual
>> in error tracking, see https://bugzilla.mozilla.org/show_activity.cgi?id=313822.
>> If the current owner can't or wouldn't work the bug, he drops it again. This
>> does no harm and might encourage others to pay attention to that bug.
>
> Done, but not all changes were made as proposed. The differences ...
> 
>> 2. Step
>> The QA contact field will not be deleted as in my last proposal. But I will
>> delete all default QA_contacts. Let me please know if someone wants to be
>> default QA contact for a module or a core section.
> 
> Done, [email protected] is now the default QA Contact for those components of
> which no module owner/maintainer is active.

Demands are now raised that these changes should be rolled back for some modules
to the old behaviour (Automatically assign new bugs to a person).  It is
explained with the need for bugzillas reminders (=whining emails).

Perhaps another change to bugzilla was unnoticed.  The predefined search "My
Bugs" now encloses all bugs where the user is QA Contact too.

Users can set that they get emails on every changes on a bug in modules which
they are QA Contact for.  So there is no difference in notifications between
Assignee and QA Contact except for reminders.

Are those reminders so valuable to step back to the old method?  To a method
that let to ~1,000 bugs which were *formally assigned* over several years but no
resolution was given?