This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Normaly if I enter a new bug I don't fill anyone in a field assigned to (because I don't have any idea). So this bug is reported to all pepole subscribed to its appropriate bug mailing list and to default component owner. (So owner of a module will receive 2 duplicated notification...). But !!!! If you know who this bug should be assigned and you do this. This bug is reported JUST ONLY to you and assigner (in others worlds, only 1 person is notificated about this bug, I don't calculate myself 'cause I know it). It couses a lot of troubles started for instance: 1.mail filters don't catch this mail (trivial) 2.only 1 person was informed and he/she could be ill,... bug could be FIX at a time !!!! 3.people aren't informed so for which purposes they subscribed into bug mailing list????!!!! could you explain it to me, please?
I'm not sure I understand the full impact. Can this problem be solved if you know who to assign the bug to and do so but remember to add bugs@<project>.netbeans.org to the "cc" list so that the proper person gets notified BUT the bugs rollup list still gets notified? I'm marking this worksforme, but I think I'm just not understanding the full problem here.
Hi Keri, I partialy agree with you. Your workaround is good and I've started to use this. But disagree that it could be the reason to say :Works For Me.... The impact/problem I reported is: All people who are subscribed into buglist of module. They SURE WANT to know ALL new BUGS and CHANGES in a module of their interest. And field "Assigned to" BREAK THIS RULE in general !!!! The fix which I will suppose is: ================================= *Always send mail to BUGLIST if new bug or some change of bug was done. That is the reason why the buglist exist. *At least to put bug-list to CC automaticaly (noone could knows which they are... and for instance the bug list of UI product is out of standard) *Or have some switch: Inform bug-list Y/N (but it also AGAINST the purpose of buglist) But I also know you are going to replace Bugzilla by Scarab, so I'd like to set verified this bug (but better for communication is to reopen). And Please you re-tell my(our) problem/need/Request of enhancement. I'll wellcome your coments thanks Daniel
I'm lowering the Severity, I don't think this is a critical issue--I agree it is annoying but we have managed to work with it so far. Manually adding the bugs@xxx.netbeans.org address to CC does the job, even if it is clumsy.
OK. And How it will be solved in Scarab?
FYI -- this issue and the corresponding one for bug-rollup lists will be resolved by upgrading to IssueZilla (see http://www.openoffice.org/issues/index.html for an example of IZ in action). In Issuezilla, we use the QA contact field in issuezilla for the project bugs list. This means that assignment of a bug to someone will not remove the bugs@<project> list from notifications on the given bug. Furthermore, in IZ, we use the "watchers" feature to duplicate all entries in the project bugs lists in the toplevel bugs list (akin to nbbugs@netbeans.org). This eliminates special-casing the rollup lists, allowing them to be config'd from the web interface. The "watchers" feature of IZ also solves the problem of people being away or ill... you can use the watch subscribe-to and watch other people's bug-streams. See http://www.openoffice.org/issues/userprefs.cgi?bank=diffs .... As this issue is resolved by an upgrade to sourcecast, I'm changing the status as "resolved later". The new issue spawned from this should be "when will we upgrade netbeans to use IssueZilla" (as has been discussed previously). We certainly will not be upgrading or fixing the old bugzilla on netbeans given that a significant improvement is available and is a supported part of "sourcecast classic" (nee tigris). Certainly IssueZilla will be the supported bug-tracker for the upcoming linux-to-solaris port and deployment of Sourcecast. It would of course reduce risk and be prudent to upgrade IssueZIlla on Linux first (and perform the necessary data/schema migration) prior to migrating sourcecast to solaris.) Of course, upgrading to issuezilla will require some scheduled downtime to the issue tracking system while the existing bug-data is migrated from bugzilla to issuezilla. This needs to be appropriately planned and communicated.
hmmm...That sounds interesting...
Long fixed...
x *** This issue has been marked as a duplicate of 8785 ***
allright
We recently moved out from Collabnet's infrastructure