I am rolling out Bugzilla at the company where I work. I am setting up a private bug database; only the people at my company may use it (or even look at it). In this situation, it seems kind of silly to have user names like "steveha@mdlcorp.com" when just "steveha" would deliver the mail just as well. Therefore I request a configurable parameter to control the email name validator. Right now it looks for an '@' and a '.' in the email name; with the preference set, it would accept anything.

Upon further thinking, I have realized that I don't really care whether Bugzilla stores a full email address or a short one. I just don't want to have to type the whole thing. So, perhaps a better solution is to have a table of shortcuts: "steveha" would map to "steveha@mdlcorp.com". Or maybe even "srh" would map onto "steveha@mdlcorp.com". This is a better general solution: it provides the convenience I want, but if we ever wanted to export the bugs to a globally-visible database, the user names would be in useful format.

Well, I liked the original solution, so I have implemented it. Nicknames are just too involved and error-prone for my tastes. You will find three new params you can tweak to make things happen.

per Terry, auto-verifying any resolved bug that hasn't been touched since before 2.10 was released.

Moving to Bugzilla product