Useful Patches and Utilities for Bugzilla
The setperl.csh Utility
You can use the "setperl.csh" utility to quickly and
easily change the path to perl on all your Bugzilla files. This
is a C-shell script; if you do not have "csh" or "tcsh" in the
search path on your system, it will not work!
Download the "setperl.csh" utility to your Bugzilla
directory and make it executable.
bash#
cd /your/path/to/bugzilla
bash# wget -O
setperl.csh
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'
bash# chmod
u+x setperl.csh
Prepare (and fix) Bugzilla file permissions.
bash#
chmod u+w *
bash# chmod
u+x duplicates.cgi
bash#
chmod a-x bug_status.html
Run the script:
bash#
./setperl.csh /your/path/to/perl
Using Setperl to set your perl path
bash#
./setperl.csh /usr/bin/perl
Command-line Bugzilla Queries
Users can query Bugzilla from the command line using this suite
of utilities.
The query.conf file contains the mapping from options to field
names and comparison types. Quoted option names are "grepped"
for, so it should be easy to edit this file. Comments (#) have
no effect; you must make sure these lines do not contain any
quoted "option"
buglist is a shell script which submits a Bugzilla query and
writes the resulting HTML page to stdout. It supports both
short options, (such as "-Afoo" or "-Rbar") and long options
(such as "--assignedto=foo" or "--reporter=bar"). If the first
character of an option is not "-", it is treated as if it were
prefixed with "--default=".
The columlist is taken from the COLUMNLIST environment variable.
This is equivalent to the "Change Columns" option when you list
bugs in buglist.cgi. If you have already used Bugzilla, use
grep COLUMLIST ~/.netscape/cookies to see
your current COLUMNLIST setting.
bugs is a simple shell script which calls buglist and extracts
the bug numbers from the output. Adding the prefix
"http://bugzilla.mozilla.org/buglist.cgi?bug_id=" turns the bug
list into a working link if any bugs are found. Counting bugs is
easy. Pipe the results through sed -e 's/,/ /g' | wc |
awk '{printf $2 "\n"}'
Akkana says she has good results piping buglist output through
w3m -T text/html -dump
Download three files:
bash$ wget -O
query.conf
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26157'
bash$ wget -O
buglist
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26944'
bash# wget -O
bugs
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26215'
Make your utilities executable:
bash$
chmod u+x buglist bugs
The Quicksearch Utility
Quicksearch is a new, experimental feature of the 2.12 release.
It consist of two Javascript files, "quicksearch.js" and
"localconfig.js", and two documentation files,
"quicksearch.html" and "quicksearchhack.html"
The index.html page has been updated to include the QuickSearch
text box.
To take full advantage of the query power, the Bugzilla
maintainer must edit "localconfig.js" according to the value
sets used in the local installation.
Currently, keywords must be hard-coded in localconfig.js. If
they are not, keywords are not automatically recognized. This
means, if localconfig.js is left unconfigured, that searching
for a bug with the "foo" keyword will only find bugs with "foo"
in the summary, status whiteboard, product or component name,
but not those with the keyword "foo".
Workarounds for Bugzilla users:
search for '!foo' (this will find only bugs with the
keyword "foo"
search 'foo,!foo' (equivalent to 'foo OR
keyword:foo')
When this tool is ported from client-side JavaScript to
server-side Perl, the requirement for hard-coding keywords can
be fixed. This bug has details.