#Bugzilla 5 install
#Bugzilla 5 code

I opted instead to install Postfix (which I also have more familiarity with), and switched Bugzilla to use the machine's sendmail ( mail_delivery_method: sendmail).

This affects all mail sent by Bugzilla, not just bug updates.Įnabling use_mailer_queue seemed to me like asking Bugzilla to run a mini sendmail daemon. This requires that you have installed certain Perl modules (as listed by for this feature), and that you are running the daemon (otherwise your mail won't get sent). If you enable this parameter, Bugzilla will queue all mail and then send it in the background. In a large Bugzilla installation, updating bugs can be very slow, because Bugzilla sends all email at once. Under Administration | Parameters | Email:

#Bugzilla 5 code

So unless it is specifically configured, all emails must be sent before the 'Save' completes.īugzilla does mention this problem, but I only found this late in the game (and after I had started putting trace logic into the Bugzilla code :). On the other hand, Bugzilla has good performance with large bug databases, an extensive grouping feature for issues and users, advanced search.The issue was, believe it or not, sending email.īugzilla has no internal way of putting email in a queue and sending it in the background. Among the drawbacks of Bugzilla in comparison to cloud-based issue trackers are its complex installation and configuration process, outdated UI, limited customizability, and lack of commercial support. Although still in use at many organizations and in many projects, it has lost some of its appeal in recent years in favour of cloud-based bug tracking tools such as Jira and GitHub. Improved caching: Bugzilla can connect to a Memcached server to reduce the number of database queries that are executed and thus improve performance.Ī complete list of changes can be found in the release notes.īugzilla, originally developed by Mozilla and made open source in 1998, was at some point a kind of standard among error tracking tools. Later, Bugzilla was written in PERL and it uses the MYSQL database. It was written by Terry Weissman in TCL programming language in 1998. Unfortunately the Make Bugzilla Pretty effort stalled and was replaced by incorporating the theme used by which also unfortunatly did not make it into 5.0, but is rescheduled to 6.0. It helps the developers and other stakeholders to keep track of outstanding problems with the product. When a site administrator creates a new user, an email is sent to the user. This new policy, though, being more relaxed, might accidentally expose bugs to the wrong people. Bugzilla is an open-source tool used to track bugs and issues of a project or a software.

Whereas in the past a user was required to belong to all groups the bug was in, a new setting, which is default in 5.0, allows anyone who belongs to any group the bug is in to view it. Membership checking: A new more flexible policy has been established to determine who can view a bug. This can be useful to thread conversations by tag, mark specific comments as important or spam, etc. A big improvement brought by the REST-like interface is support for API key, so clients do not need to use cookies or a user’s credentials.īug comment tags: Tags can now be used to filter bug comments. The already existing XML-RPC and JSON-RPC endpoints have been deprecated and will be likely removed in Bugzilla 7.0. WebServices API: Bugzilla 5.0 adds a new REST-like endopoint that will allow clients to use standard HTTP calls. The bug tracking tool adds many new features and improvements, such as the ability to add tags to comments, new group membership checking, improved web service API, and more. Two years after its last release, Bugzilla has reached version 5.0.