aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* A few changes ...seth%cs.brandeis.edu2000-03-163-50/+270
| | | | | | | | 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.
* Add a "send mail to bug owners" link (under circumstances where itterry%mozilla.org2000-03-161-0/+14
| | | | seems useful and appropriate.)
* updated to better reflect reality in terms of recent changes to bug_email.pl.seth%cs.brandeis.edu2000-03-151-6/+15
|
* Sigh. We now need to lock the attachments table, too, just in case aterry%mozilla.org2000-03-111-1/+1
| | | | | midair collision happens which needs to generate text which needs to look at the attachments table. Sigh.
* updated to reflect that only specific versions of GD.pm and Chart will work.dmose%mozilla.org2000-03-112-20/+22
|
* Whoops; left out the "mailto:" part of a mailto link.terry%mozilla.org2000-03-111-3/+3
|
* Italicize the "Additional Comments From" stuff, so that you can tellterry%mozilla.org2000-03-115-96/+134
| | | | | the difference between new comments and people copying stuff in from old comments.
* Removed warning.terry%mozilla.org2000-03-111-1/+3
|
* Never let ", <, or > be matched as part of a URL.terry%mozilla.org2000-03-111-1/+1
|
* Patch by Joe Robins <jmrobins@tgix.com> -- allow automatic definitionterry%mozilla.org2000-03-115-18/+335
| | | | | | | of a group per project, and automatically put new bugs against that project into that group, thus allowing entire projects to be protected against viewing by unauthorized users. This is all optional, controlled by new parameters.
* Patch by "Peter Schweiger" <Schweiger.Peter@litef.de> -- minor bugfixes.terry%mozilla.org2000-03-102-1/+3
|
* Whoops; removed extra double-quote.terry%mozilla.org2000-03-081-1/+1
|
* Patch by Dave Miller <dave@intrec.com> -- allow setting ofterry%mozilla.org2000-03-082-10/+52
| | | | confidentiality when submitting a new bug.
* Patch by Peter Schweiger <schweiger.peter@litef.de> -- date formattingterry%mozilla.org2000-03-082-3/+3
| | | | string wasn't working with modern MySQL engines.
* Oops! canconfirm bit wasn't actually working.terry%mozilla.org2000-03-081-16/+9
|
* Was choking on order='Importance'.terry%mozilla.org2000-03-081-2/+2
|
* * this adds in DEFAULT_PRODUCT and DEFAULT_COMPONENT functionality to theseth%cs.brandeis.edu2000-03-081-5/+20
| | | | bug_email.pl script. See comments in the script itself for how it works.
* added hack for NSS bug injectiondmose%mozilla.org2000-03-081-1/+4
|
* Fixed stupid syntax error in last patch.terry%mozilla.org2000-03-081-1/+1
|
* Patch by "David Gardiner" <david.gardiner@unisa.edu.au> -- recognizeterry%mozilla.org2000-03-081-0/+3
| | | | more useragent strings.
* Patch by Brian Duggan <bduggan@oven.com> -- security improvements.terry%mozilla.org2000-03-086-5/+13
|
* Contribution by Eli Goldberg <eli@prometheus-music.com> -- genericterry%mozilla.org2000-03-082-1/+282
| | | | bug-writing guidelines.
* Submission by Klaas Freitag <freitag@suse.de>.terry%mozilla.org2000-03-083-0/+299
|
* Patch by Olaf Krische <krische@mbi-berlin.de> -- Fixed HTML typos.terry%mozilla.org2000-03-081-2/+2
|
* Fixed very stupid typo.terry%mozilla.org2000-03-071-1/+1
|
* Make a universal routine to report errors in forms, so that we canterry%mozilla.org2000-02-265-95/+60
| | | | have a universal (and more noticable) way of displaying them.
* If there is only one project allowing new bugs, don't bother promptingterry%mozilla.org2000-02-261-3/+12
| | | | for which project to use.
* Fixed to cope with new longdescs table.terry%mozilla.org2000-02-251-2/+13
|
* Cut down on the number of syncshadowdb processes we fork off.terry%mozilla.org2000-02-192-2/+12
|
* Don't stomp on bugs timestamps when adding the new everconfirmed field.terry%mozilla.org2000-02-191-1/+1
|
* Check that we have defined a shadow db before trying to use it.terry%mozilla.org2000-02-191-1/+1
|
* Make reports work off of the the shadow database.terry%mozilla.org2000-02-181-1/+1
|
* Fixed some functions in buglist.cgi that won't work if we're hooked upterry%mozilla.org2000-02-182-3/+10
| | | | to the shadow database.
* Wasn't always tweaking LOCK TABLES commands correctly when shadowing. And ↵terry%mozilla.org2000-02-181-3/+3
| | | | finally fixed it to actually generate useful SQL error messages.
* Added an optional ability to keep a read-only shadow database, so thatterry%mozilla.org2000-02-188-8/+224
| | | | | bug queries can be run against it, so that these slow queries won't be able to tie up the rest of the system.
* Fixed bug where it was complaining that people without permissionsterry%mozilla.org2000-02-181-0/+6
| | | | were changing the resolution, even if they weren't.
* Was crashing when logging profile activity.terry%mozilla.org2000-02-181-3/+6
|
* Oops; had the name of the "editbugs" group typed in wrong in a coupleterry%mozilla.org2000-02-172-3/+3
| | | | of places.
* Display all possible state transitions in a bug if the user is notterry%mozilla.org2000-02-172-4/+14
| | | | | | logged in. Since they haven't logged in, we don't know what they will be allowed to do. And users who disable cookies tend to pretty often not be logged in.
* Put the "users" link in the trailer for people who are able to tweakterry%mozilla.org2000-02-171-4/+4
| | | | the permissions of other users.
* Ignore leading and trailing whitespace when trying to decide ifterry%mozilla.org2000-02-171-0/+3
| | | | someone changed something.
* Removed stupid debugging printf.terry%mozilla.org2000-02-171-1/+0
|
* Fixed icky infinite loop bug.terry%mozilla.org2000-02-171-3/+4
|
* Was crapping out if strictvaluechecks was turned on.terry%mozilla.org2000-02-171-17/+17
|
* Major spankage. Added a new state, UNCONFIRMED. Added new groups,terry%mozilla.org2000-02-1716-186/+942
| | | | | | | | | | | | "editbugs" and "canconfirm". People without these states are now much more limited in what they can do. For backwards compatability, by default all users will have the editbugs and canconfirm bits on them. Installing this changes as is should only have one major visible effect -- an UNCONFIRMED state will appear in the query page. But no bugs will become in that state, until you tweak some of the new voting-related parameters you'll find when editing products.
* Lock the tables as low-priority when writing. Maybe makes people making ↵terry%mozilla.org2000-02-161-1/+6
| | | | changes wait longer, but people doing read-only stuff should now never block for very long.
* Patches by Ken Jenks <kjenks@abiblion.com> and jug@tellux.de -- make the ↵terry%mozilla.org2000-02-161-2/+3
| | | | Javascript behave under IE5 and under Netscape 3.x
* Patches by Ken Jenks <kjenks@abiblion.com> and jug@tellux.de -- make the ↵terry%mozilla.org2000-02-151-16/+11
| | | | Javascript behave under IE5 and under Netscape 3.x
* This implements canonical email address transformation. i.e., you have the ↵seth%cs.brandeis.edu2000-02-131-9/+33
| | | | 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.
* o this is a minor step towards getting canonical email addresses to work, ↵seth%cs.brandeis.edu2000-02-131-9/+41
| | | | | | | | 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.
generated by cgit v1.2.1 (git 2.21.0) at 2024-10-02 15:22:18 +0000