On Mon, 10 Mar 2008, Craig Dunigan wrote:

> On Sat, 8 Mar 2008, David Miller wrote:
>> Craig Dunigan wrote on 2/20/08 12:48 PM:
>>> Just noting this so it will appear in mail archive searches. This
>>> code tweak to Bugzilla::User actually handles about half the places
>>> where an email address is displayed, so it didn't turn out to be as
>>> clean as I'd hoped. The other half does require at least the template
>>> tweaks noted in https://bugzilla.mozilla.org/show_bug.cgi?id=219021 ,
>>> plus a few, and tiny bit more code change.

>> It would be great if you could get the updated patch for this added to
>> one of those two bugs, too. Lots of people have been clamoring for
>> that, more for spam protection than trying to protect people from each
>> other. It's just a semi-complicated thing to pull off with Bugzilla's
>> current architecture, as you noted.
>> The other part of the problem of course comes to adding people to the CC
>> list, assignees, etc. If you can't use their email address, how do you
>> identify them? Bugzilla doesn't really have a unique user identifier
>> other than the email address currently, and if you did add one, how
>> would you create IDs for existing users that may or may not log in to
>> see a prompt asking they create an ID?

> Heh. I just realized the bit about the CC list myself. I'm working
> on it. Do you want the patch for "no email display" before or after I
> get the CC thing worked out?

Re-reading that, I realized that my brevity engendered obscurity.
In my haste, I didn't actually address the issue you mention at all.
I meant that I intend to work out how to suppress display of addresses
on the CC list, which the changes I mention previously do not cover,
not that I intend to work out how to create a new unique user
identifier that can be used for assigning bugs. It looks like
https://bugzilla.mozilla.org/show_bug.cgi?id=218917 starts to address
that issue. My intention for my own situation is to allow only the
developer group to assign bugs, and allow that group to see all
addresses with the drop-down list option in the assign and CC fields.
Default assignee for components that don't currently have a real
default assignee will be a joint list address that goes to all
developers, probably with a "real name" that looks something like "Not

For the "official" patch, would it be beneficial for me to code it so
that I replace "developer group" with "logged in user," and make the
display suppression also dependent on login status? Is that what most
people actually want?

Craig Dunigan
IS Technical Services Specialist
Middleware - EIS - DoIT
University of Wisconsin, Madison

opinions expressed are my own, not the University's