| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
the email interface after they were changed to userid's in bug 66876.
r= justdave@syndicomm.com
|
| | |
|
| |
|
|
| |
patch submitted by brad@xyu.dhs.org (Brad Sarsfield)
|
| |
|
|
| |
bug_email.
|
| |
|
|
|
|
|
|
| |
1. BugzillaEmail.pm is a (kinda, sorta) module which is going to hold the various code which is common between all the scripts which access bugzilla via email.
2. bug_email.pl uses this module
3. bugzilla_email_append.pl is a mostly ready script which will append messages to existing bugs.
|
| |
|
|
| |
bug_email.pl script. See comments in the script itself for how it works.
|
| |
|
|
| |
option of setting up bug_email.pl to search the profiles database for a username which has the same username (before the @) same username and base domain (seth@cs.brandeis.edu = seth@job.cs.brandeis.edu) or identical email address (old behavior) based on the From email address. See the code for a more sensical description.
|
| |
|
|
|
|
|
|
| |
and not via a gross hack (the script with a gross hack is in use in a production environment, so ...)
Anyways, this address the findUser() sub and email transforms of none, base domain, and name only. base_domain is not properly implemented yet. an email transform of none does an exact match on email addresses in the profiles table. A name only transform does a regular expression match (via mysql's RLIKE operator) on the name portion of the address (i.e., seth from seth@job.cs.brandeis.edu). This is sloppy, but useful in an environment where there are only a few users.
the base_domain is next, probably tomorrow. I need to figure out how to implement it first.
|
|
|
tree under the contrib directory. This is not my code, but I'm championing its maintanence right now, since I'm using and hacking on it heavily. The list of contributors can be found in the file itself.
Changes I've made :
- updated to the newest CVS pull of bugzilla
- works out of contrib/bugzilla
- put in the MPL license header
Directions for use are in the file itself. Essentially, you put in a procmailrc entry which cats the message to this script.
Changes coming in the near future ...
- canonical email transformation (i.e., seth@job.cs.brandeis.edu == seth@cs.brandeis.edu)
- default product and component (i.e., if you don't specify a product and component, it goes into a PENDING product)
- querying a bug over email
- appending a bug over email
- keywords over email
- use the globals.pl parameters functionality to edit and save this script's parameters
- integrate some setup in the checksetup.pl script
FWIW, the first two things are necessary for this to be useful in my setup, so they get an overwhelming bit of priority
|
