The Bugzilla Guide - 2.22 Release
Prev | Chapter 5. Customising Bugzilla | Next

# 5.3. Customizing Who Can Change What

| This feature should be considered experimental; the Bugzilla code you will be changing is not stable, and could change or move between versions. Be aware that if you make modifications as outlined here, you may have to re-make them or port them if Bugzilla changes internally between versions, and you upgrade.

Companies often have rules about which employees, or classes of employees, are allowed to change certain things in the bug system. For example, only the bug's designated QA Contact may be allowed to VERIFY the bug. Bugzilla has been designed to make it easy for you to write your own custom rules to define who is allowed to make what sorts of value transition.

For maximum flexibility, customizing this means editing Bugzilla's Perl code. This gives the administrator complete control over exactly who is allowed to do what. The relevant function is called `CheckCanChangeField()`, and is found in `process_bug.cgi` in your Bugzilla directory. If you open that file and search for "sub CheckCanChangeField", you'll find it.

This function has been carefully commented to allow you to see exactly how it works, and give you an idea of how to make changes to it. Certain marked sections should not be changed - these are the "plumbing" which makes the rest of the function work. In between those sections, you'll find snippets of code like:

        # Allow the assignee to change anything.
        if ($ownerid eq $whoid) {
            return 1;
        }

It's fairly obvious what this piece of code does.

So, how does one go about changing this function? Well, simple changes can be made just by removing pieces - for example, if you wanted to prevent any user adding a comment to a bug, just remove the lines marked "Allow anyone to change comments." If you don't want the Reporter to have any special rights on bugs they have filed, just remove the entire section that deals with the Reporter.

More complex customizations are not much harder. Basically, you add a check in the right place in the function, i.e. after all the variables you are using have been set up. So, don't look at $ownerid before $ownerid has been obtained from the database. You can either add a positive check, which returns 1 (allow) if certain conditions are true, or a negative check, which returns 0 (deny.) E.g.:

        if ($field eq "qacontact") {
            if (Bugzilla->user->groups("quality_assurance")) {
                return 1;
            }
            else {
                return 0;
            }
        }

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.

| 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 in `data/versioncache` for the list called `@::log_columns`. If you need help writing custom rules for your organization, ask in the newsgroup.

Prev | Home | Next
Template Hooks | Up | Modifying Your Running System