Blog

Bugs Dashboard uses the Bugzilla web service to authenticate users to the application. It does not store any username or password locally. A user must exist in the Bugzilla database with the password provided in the login form, but more importantly, Bugs Dashboard must be able to communicate with Bugzilla via the web service. As …

v3.4.5 introduced significant changes to the underlying storage and manipulation of properties, introduced several new widgets and fixed several bugs. Our attention is now on v3.5 and we wanted to share some of the major changes forthcoming in it. Restrict Reporting By Classification, Product, Component and/or Milestone v3.5 will introduce a new capability allowing you …

With version 3.4.5, we are pleased to introduce the Scorecard Widget. This widget allows you to set thresholds for key performance indicators (KPI). It then queries Bugzilla to measure performance against your KPI thresholds and reports performance in standard red, yellow, green colors. The Scorecard Widget introduces an ability to edit the features of a …

I recently upgraded the Bugs Dashboard server to RedHat Enterprise Linux 6 (RHEL6) and when doing so, I installed the latest version of each of the databases we use (see my personal blog). When using PostgreSQL 9.04, I encountered a very nasty problem whereby Bugzilla appeared to be attempting to reinstall each table. The problem …

If you’re installing Bugzilla 4.x and during the execution of checksetup.pl, you encounter the following: To attempt an automatic install of every required and optional module with one command, do: /usr/bin/perl install-module.pl –all Attempt to reload DateTime.pm aborted. Compilation failed in require at Bugzilla/Util.pm line 53, line 522. BEGIN failed–compilation aborted at Bugzilla/Util.pm line 53, …

Where does your project score? In the red? Are your scores in the yellow? Or, is your project functioning so well that all your key performance indicators (KPI) are in the green? The Scorecard widget, introduced in Bugs Dashboard v3.4.5, is about to tell you how you score! The Scorecard widget is intended to provide …

Version 3.4.5 will include the ability to create widgets using PHP. You can create a simple PHP page, such as the following: <?php echo “<h1>Hello from the PHP test page</h1>” ?> Then, create a widget entry that points to your php page, such as the following: portlet41.title=PHP Widget portlet41.package=com.wmpnj.bugz.widgets.PhpWidget portlet41.method=getText portlet41.stylesheet=phpwidget.css portlet41.javascript=plainajax.js portlet41.desc=Allows Ajax calls …

Over the past three years, I have served as the ScrumMaster for an ongoing, evolving project with two different teams. The project transitioned from R&D at one company and is currently in the stages of implementation in a production environment at another company. During my work on these projects, I have employed either the Basic …

In a previous post, we looked at how to deploy under Ubuntu 7.10 by downloading, decompressing, and then moving the “bugs” directory to the Tomcat webapps directory. In this post, we will look at deploying with the Tomcat Manager. Prerequisites All steps to download, decompress, and configure the Bugs Dashboard are the same as those …

The following are steps we take in deploying the Bugs Dashboard to a test platform running Ubuntu 7.10. Under this method, we do not use the Tomcat Manager to deploy; we’ll look at that in another post. Prerequisites Tomcat has been successfully installed (see Installing Tomcat 6 on Ubuntu at the How-to Geek) MySQL (see …