Sometimes you need bugzilla.mozilla.org’s configuration changed – components, milestones or flags added, embarrassing attachments annulled, that sort of thing. Fortunately, we have a crack team of admins who deal with these requests, mostly within 24 hours. But for super-speed, it helps if you provide all the required information up front.
Fortunately, there is now a Bugzilla Administration wiki page which lists the info you need to provide for each sort of request. Consult that first and do what it says, and you are more likely to get hyperspeed service.
Jesse Ruderman’s TidyBug GreaseMonkey script (docs) turns this:
Everyone who uses Bugzilla seriously gets a lot of bugmail. Bugzilla provides controls so you can restrict the amount of it you get. But did you know it also adds headers to each email so you can do further filtering on the client side?
Here are a sample set of headers, with explanations:
||(the role you have on the bug which led to you getting the mail; other values are AssignedTo, QAcontact)
||(other value is ‘new’)
||(the role of the person you are watching, and who it is, if you are getting bugmail for that reason)
||(the person who made the change)
||(the names of the fields changed by the update)
The following headers give the values of particular bug fields after the change in question has been made.
You can use any of these, or a combination, as a trigger to do something different with a bugmail – file it somewhere, tag it, mark it as read or delete it.
To set up filters in Thunderbird 3, go to Tools | Message Filters… . If you click “New” to add a new filter, and then scroll down to the bottom of the list of headers and other values you can filter on, you will find “Customize…” This allows you to enter custom header values, such as the X-Bugzilla headers above.
Comments Off on Client-Side Bugmail Filtering
It’s fairly easy to create a URL which does a search for “bugs reported by email@example.com“. Whoever clicks it, you get the same thing – all bugs reported by that particular user. But you can also create a URL which does a search for something like “bugs reported by the user running this search”. This means you can share it with others, and have them find the bugs which apply to them.
This is done with “pronouns”. These only work with boolean charts (bug). The left hand side of the chart can be any field which expects an email address. The operator must be “is equal to” or “is not equal to”. The right hand side then can be of the following values: “%reporter%”, “%assignee%”, “%qacontact%”, or “%user%”. These do exactly what you might expect.