Issue 118596 - Side effect of closure mailing list in Bugzilla
Summary: Side effect of closure mailing list in Bugzilla
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Bugzilla (show other issues)
Version: current
Hardware: PC Windows 7
: P5 (lowest) Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2011-11-11 13:18 UTC by r4zoli
Modified: 2013-01-23 01:40 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description r4zoli 2011-11-11 13:18:17 UTC
The closure of all mailing list running on discussed on ooo-dev@i.a.o list.
One side effect will be default assignee in Bugzilla, who is responsible for the bug will be abandoned. Every Product has own default assignee, such as for this bug is: Other examples,

In past they used as a waiting list, until the developers appointed, not spam all developers mailing lists, possibly used inside sun/oracle.
Usually when QA reviewed bug, assigned developer, or if the bug not confirmed the default mail used as sink.   

I have no knowledge where these mails posted now. 
They needs to substituted until the closure happens.

Possible solution use ooo-issues mailing list instead cc-ing.

Another problem could be the already assigned bugs, where email addresses used.
Comment 1 T. J. Frazier 2011-11-11 15:17:25 UTC
The good news is that changing the email address for an account (like issues@) will change all the displayed references. A BZ administrator should be able to do that. All we have to decide is, what to change it to?
Comment 2 Oliver-Rainer Wittmann 2012-06-13 12:31:39 UTC
getting rid of value "enhancement" for field "severity".
For enhancement the field "issue type" shall be used.