Monthly Archives: March 2010

Filtering Bugzilla Bugmail in Gmail

Found this little gem and it got me thinking about how to make this happen in Gmail.

Turns out, you can’t filter by arbitrary email header, so the best you can do is use the ones that are supported.

How To Delete Bugs in Bugzilla

A regular questions that comes up regarding Bugzilla is: “How do I delete bugs in Bugzilla?”

The standard answer is that you don’t and you shouldn’t. They usually give good reasons like maintaining history etc. However, there are certainly times (although infrequent) when it is appropriate to delete a bug.

There are some administrative settings you will most like have to change before you can delete a bug. (note: I am referring to Bugzilla 3.4.6) Log in with an account belonging to the admin group and navigate to the Administration page. Then go to the Parameters page. Finally choose the Administrative Policies link. (Administration -> Parameters -> Administrative Policies)

Now you will see the allowbugdeletion parameter which is most likely set to off unless you’ve been fiddling with it while trying to delete a bug. Change the parameter to on and click Save Changes. There is a key hint in the description of this parameter.

The pages to edit products and components can delete all associated bugs when you delete a product (or component). Since that is a pretty scary idea, you have to turn on this option before any such deletions will ever happen.

Note the bolded phrase.  You can’t directly delete bugs, you must assign a bug to a component or product and delete it. This bears repeating – you cannot delete a bug directly.

The easiest way is to create a component in the product with the bugs you want to delete. Call it “Trash” or something equally descriptive. Now find the bugs you want to delete and change their component to “Trash”.

Once you have added all the soon to be deleted bugs to your trash component go back to the component list in the administration page (Administration -> Products -> <your product> -> Edit Components). You should see an “Action” column on the far right of the table with all your components with a Delete link. Find your trash component and click the associated “Delete” link.

You will be presented with a confirmation page with a big red warning telling you how many bugs will be deleted. You can view the bug list to verify or just click the “Yes delete” button.

Your bugs are now deleted.

You will most like want to turn the allowbugdeletion parameter off again to prevent accidents.

TikiWiki Upgraded to 4.2

New Features


  • Full support for OpenID
  • Multiple improvements for LDAP authentication


  • Assign default size for images


  • Allow wiki comments on a per-page basis


  • Multiple theme, CSS, and UI improvements

Full Feature List

No Hassle Open Source Project Management Hosting

MantisBT Upgraded to 1.2.0

There are many new features added to 1.2.0, including:

  • Global categories available to all projects, as well as project categories inheriting from parent projects to child projects; both are optional
  • Tracked change history for textarea fields (Description, etc) and bug notes
  • Customizable sets of columns for View Issues page and export formats
  • Combined simple and advanced views into a single, configurable view that allows selecting exactly what fields to show or hide
  • Improved roadmap and changelog pages, including version release dates, and permalinks to individual versions
  • Marking versions as obsolete to hide them from the roadmap and changelog
  • More configuration options for rebranding MantisBT installations
  • Improved support for UTF-8 localizations and content
  • Implemented custom search providers for Firefox and Internet Explorer
  • Implemented localized timestamps using according to user-preferred timezones

Full Changelog

No Hassle Open Source Project Management Hosting

Bugzilla updated to 3.4.6

All Bugzilla instances have been updated to 3.4.6. You can read about all the changes here or just the differences below.

  • When doing a search that involves “not equals” or “does not contain the string” or similar “negative” search types, the search description that appears at the top of the resulting bug list will indicate that the search was of that type. (Bug 474738)
  • In Internet Explorer, users couldn’t easily mark a RESOLVED DUPLICATE bug as REOPENED, due to a JavaScript error. (Bug 546719)
  • If you use a “bookmarkable template” to pre-fill forms on the bug-filing page, and you have custom fields that are only supposed to appear (or only supposed to have certain values) based on the values of other fields, those custom fields will now work properly. (Bug 538211)
  • If you have a custom field that’s only supposed to appear when a bug’s resolution is FIXED, it will now behave properly on the bug-editing form when a user sets the bug’s status to RESOLVED. (Bug 520993)
  • If you are logged-out and using request.cgi, the Requester and Requestee fields no longer respect the usermatching parameter–they always require full usernames. (Bug 533018)
  • If you tried to do a search with too many terms (resulting in a URL that was longer than about 7000 characters), Apache would return a 500 error instead of your search results. (Bug 513989)
  • Bugzilla would sometimes lose fields from your sort order when you added new fields to your sort order. (Bug 470214)
  • The Atom format of search results would sometimes be missing the Reporter or Assignee field for some bugs. (Bug 537834)
No Hassle Open Source Project Management Hosting