Archive for the 'Bug tracking' Category


Thursday, February 26th, 2009

My newest Greasemonkey script, TidyBug, cleans up the show-bug page on

TidyBug hides empty fields, making it easier to see the fields that are populated and reducing the amount of scrolling needed to see the comments. In the example above, TidyBug removed 61% of the space above the first comment (from 985 pixels to 381 pixels). Even on busy bugs, such as upvar2, TidyBug makes the bug considerably cleaner (upvar2 screenshot).

Some other things TidyBug does:

  • Makes form control borders only appear on hover to reduce visual noise.
  • Hides four fields that are mostly useless in bmo (version, architecture, OS, severity).
  • Adds keyboard shortcuts for accessing hidden fields and several common actions.
  • Clicks the "hide obsolete attachments" link for you.

Is this useful for many people? Should parts of it be uplifted into or the Bugzilla distribution? What new keyboard shortcuts or other features would you like to see?

Earth complaint department

Wednesday, April 23rd, 2008

Finally, a bug-tracking system for everything. The priorities, severities, products, and components are great.

How I search for bugs

Wednesday, August 13th, 2003

People often ask if I memorize bug numbers. I've only memorized a few bug numbers; my speed comes from having memorized parts of bug summaries and these searching tricks:

  • I use Bugzilla QuickSearch for 99% of my searches. I only use query.cgi when I need "changed in n days" or things only available in boolean charts (such as bug history).
  • I include resolved bugs in most of my searches (using "ALL") so I can follow links from duplicates.
  • I restrict my searches to bugs with 2 or mote votes (using "votes:2") when I search for a bug I know is "popular". About 9% of open bugs have 2 or more votes.

I also change bugs so I can search for them more easily.

  • I change summaries to make bugs show up in searches by adding words that I'm likely to search for.
  • I change summaries to make them easy to understand in search results by making them more precise or shorter.
  • I cross-reference bugs that are closely related by adding a comment to each bug pointing to the other bug.

If I know that two bugs are cross-referenced, I often use the "collect buglinks" bookmarklet instead of skimming comments for the link.