Chapter 6. Customizing Bugzilla This says that only users in the group "quality_assurance" can change the QA Contact field of a bug. Getting more weird: if (($field eq "priority") && (Bugzilla->user->email =~ /.*\@example\.com$/)) { if ($oldvalue eq "P1") { return 1; } else { return 0; } }
This says that if the user is trying to change the priority field, and their email address is @example.com, they can only do so if the old value of the field was "P1". Not very useful, but illustrative.
Warning If you are modifying process_bug.cgi in any way, do not change the code that is bounded by DO_NOT_CHANGE blocks. Doing so could compromise security, or cause your installation to stop working entirely.
For a list of possible field names, look at the bugs table in the database. If you need help writing custom rules for your organization, ask in the newsgroup.
6.5. Integrating Bugzilla with Third-Party Tools 6.5.1. Bonsai Bonsai is a web-based tool for managing CVS, the Concurrent Versioning System . Using Bonsai, administrators can control open/closed status of trees, query a fast relational database back-end for change, branch, and comment information, and view changes made since the last time the tree was closed. Bonsai also integrates with Tinderbox, the Mozilla automated build management system.
6.5.2. CVS CVS integration is best accomplished, at this point, using the Bugzilla Email Gateway. Follow the instructions in this Guide for enabling Bugzilla e-mail integration. Ensure that your check-in script sends an email to your Bugzilla e-mail gateway with the subject of “[Bug XXXX]”, and you can have CVS check-in comments append to your Bugzilla bug. If you want to have the bug be closed automatically, you’ll have to modify the contrib/bugzilla_email_append.pl script. There is also a CVSZilla project, based upon somewhat dated Bugzilla code, to integrate CVS and Bugzilla through CVS’ ability to email. Check it out at: http://www.cvszilla.org/.
92