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.

Bug 6973 - No way to include arbitrary email in CC field
Summary: No way to include arbitrary email in CC field
Status: RESOLVED INVALID
Alias: None
Product: obsolete
Classification: Unclassified
Component: collabnet (show other bugs)
Version: 3.x
Hardware: PC Linux
: P2 normal (vote)
Assignee: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-07-04 11:54 UTC by Jesse Glick
Modified: 2009-11-08 02:26 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2000-07-04 11:54:59 UTC
If you are reporting a bug on someone's behalf, you might reasonably want to
place them in the CC field for the bug so that they get email when the status of
the bug changes. But Bugzilla does not permit this unless they have a registered
Bugzilla account (under that exact email address).
Comment 1 support 2000-07-04 17:58:59 UTC
This is unfortunately, just the way bugzilla works. We'd like to hold off
on any major reworkings of bugzilla as we intend to replace it with
scarab.tigris.org ... thus the "WONTFIX" status. (I'm not trying to be
mean about this, just realistic :-)).

One could consider the current behavior a "feature" as it prevents
people not registered in the system from getting spam if they didn't
sign up. Currently only registered bugzilla users with known-valid email
addresses can be assigned bugs or cc'd on bugs.
The email addy is known-valid because when the user
registered (in bugzilla) they are sent an email confirmation. I believe
the account only becomes active once they've responded to the confirmation
URL.

For consistency and ease-of-use, I do suggest setting up all users in
bugzilla as <cvsuser>@netbeans.org since tigris maintains the
<cvsuser>@netbeans.org mapping to the real user's email address.
Furthermore, there is additional consistency because <cvsuser> is
the same as the given user's CVS login under which they've committed
changes.

See http://www.netbeans.org/www-dev/msg00055.html for my suggestion in
this regard. This will require a remapping of all existing
<userfirst>.<userlast>@netbeans.com names to <cvsuser>@netbeans.org in the
bugzilla database. Once that is done' all you have to do is remember the
user's <cvsuser>@netbeans.org address when assigning or ccing a bug. And
one would expect all users being assigned or cc'd bugs on netbeans.org to
have a netbeans.org account already setup...

For CC'ing users not in the system.... there is no solution currently. One
possiblity is to CC bugs@<module>.netbeans.org and tell the user to monitor
the archive at http://<module>.netbeans.org/<module>-bugs/ to see if their
bug got fixed.

I do think that having a way of browsing valid addresses in bugzilla
(both for assigned-to and CC fields) is a good and necessary idea. Furthermore,
so is the ability to easily add a 3rd party to the registered users list
(w/ an opt-in email sent out that confirms/enables the account).

This is something we expect to have in scarab because it will be better
integrated with tigris' user management.

(PS: note that bugzilla code is "write once, rewrite everywhere" Perl
spaghetti so we are reticent to do major infrastructural rework, other than
fixing showstoppers in netbeans' bugzilla. There is a very good chance that
adding a feature will break something else that'll be nearly impossible
to test for... thus the "wontfix" status until we can employ a more
manageable bug-tracking solution.)
Comment 2 Martin Ryzl 2000-11-21 12:45:59 UTC
*** Bug 8493 has been marked as a duplicate of this bug. ***
Comment 3 jcatchpoole 2001-10-29 11:04:06 UTC
reopening; there are now 5 issues about this, trying to tie them
all together.
Comment 4 jcatchpoole 2001-10-29 11:05:33 UTC

*** This issue has been marked as a duplicate of 13726 ***
Comment 5 Marian Mirilovic 2009-11-08 02:26:39 UTC
We recently moved out from Collabnet's infrastructure