Software Configuration

for an open source world

Bugzilla, TRAC, JIRA Comparison

configuration managment system Posted by Rob Castellow


Bugzilla, Jira and Trac are all popular forms of issue tracking software. They are software applications that focus on tracking reported software bugs that may be present within a programmers work. Users of open source software packages are able to directly enter a bug report. Alternatively, a company concerned with software development may choose to use an internal system. Issue tracking software is generally incorporated with other project running programs. 

A big tracking system generally utilizes a core database, in which facts relating to bugs are tracked and recorded. The information gathered may include the name of the bug, the date and time it was reported, the effect it is likely to have on programs, and the seriousness of each recorded bug. Bug tracking systems generally allow for permission, deletion, or movement of the bugs encountered by an administrator.

Some companies use bug tracking systems in order to report on the progress of their bug fixing programs. Most individual everyday computer users would use issue tracking software to eliminate anything nasty that they have accidentally collected into their computer system whilst surfing the net. LBT refers to local bug tracker, and is a program used by support professionals to keep a track of bugs and any arising issues for report to software developers. 

Bugzilla is a web-based defect tracking system that was created by the Mozilla foundation and is issued under MPL (Mozilla Public License). It was first written by Terry Weissman using the Tcl language. The implementation language for Bugzilla is now Perl. Perl was considered the better language option prior to the official release of Bugzilla, as Perl was by far the more popular language at that time. Once Perl was implemented, Bugzilla was known as Bugzilla 2.0 and made available to the general public.

Bugzilla is a general purpose bug tracker, often used by everyday people as well as professionals. It has been available since September of 1998, when it was released by Netscape Communications. This makes it one of the first defect tracking choices to have become available. Tara Hernandez took over from Terry Weissman in April of 2000. She then passed the honors along to Dave Miller in July of 2001. In May of 2007, Bugzilla 3.0 was released with many upgrades including the interface and custom fields. Bugzilla was last known to have been updated in August of the current year.

The user interface for Bugzilla is varied and includes web, e-mail, RSS, Web service and command-line. Bugzilla utilizes MySQL or PostgreSQL as back end. CVS, Subversion, Perforce and AccuRev, are all options for source code revision control system integration in regard to Bugzilla.

In respect of dynamic documentation integration and/or generation, Bugzilla allows for reporting in the format of integrated charts and reports, as well as scheduled reports via mail. In relation to test plan integration, Bugzilla offers Testopia at http://www.mozilla.org/projects/testopia/. Feature requests may also be made via Wiki. For up to date information on new or disturbing bugs, you can access such information at https://bugzilla.mozilla.org where there is also opportunity to obtain help with Bugzilla, offer feedback, or report a bug.

Bugzilla does not offer a customizable workflow option. It does have Unicode support. LDAP user authentication is included with Bugzilla. With Bugzilla, users can track the bug status in their applications. It is one of the better known defect tracking software options, and includes an advanced reporting capability.  Bugzilla is configurable. It is popular with Linux users, but will also run on any server supporting CGI. Platforms include Solaris, xBSD, Win32, and MacOS X.

Jira comes from Atlassian Software Systems and is free of license for non commercial usage. (Open source projects and any organization that is non-profit, government, academic, commercial, political, or secular may obtain Jira for free.) If you fail to qualify for free usage, a payment of between US$1200 and US$4800 is required, although if you fall into the academic category you also obtain a 50% discount. Developer groups utilizing Jira include JBoss, Spring Framework, OpenSymphony and Codehaus.

Jira is not an acronym as in the case of many programs and software choices. The title comes from the word Gojira, which refers to Godzilla in Japanese. Jira was first launched in 2003. September the second 2008 is the latest recorded instance of Jira having been updated. Other than its bug tracking usage, Jira is also a tool that can be used for project management, development assistance, or group task cataloging.

Jira offers a customizable workflow option for those seeking such as a part of their bug tracker package.  Jira comes with Unicode support. LDAP user authentication is offered within the Jira package. As regards source code revision control system integration, Jira offers several options. These currently are ClearCase, AccuRev, Perforce, CVS and Subversion.

Jira uses the Java language for implementation. Jira's user interface involves the Web, e-mail, and RSS. Jira has many options in regard to back end. These include DB2, Firebird, HSQLDB, MaxDB, MySQL, Oracle, PostgreSQL, SQL Server, and SybaseASA. It clearly stands out as having the most options for back end out of all the popular options for bug tracking systems. .

Concerning document integration, Atlassian Confluence handles Jira's Wiki enterprise. Jira has a continuum of testing and integration via plugin from Atlassian Bamboo. For detailed information on the Jira product concerning issues, reporting, statistics, workflow and extensible platform, you can go to http://www.atlassian.com/software/jira/default.jsp

One of the specialized features of Jira's version of issue tracking software is multi-dimensional reporting. The reports can be read in a variety of dimensions, including pie chart, linear or column graphs, and statistical tables. Data can reflect the amount of issues for each individual customer, the number of issues reported over a specific time frame - such as day, week, month or year, the average time to resolve an issue, and many other options.   

A customizable dashboard with project reports and statistics is amongst the other benefits of the Jira system. The home page 'dashboard' can be constructed to your personal tastes. You might opt to view project statistics, line graphs or pie charts, or a project list. HTML text messages are another option for dashboard display, as are a list of assigned issues. You choose what you see and where, with all portlets being fully customizable. You can also choose to have more than one base page, and/or share the page(s) with others.

Trac is a product of Edgewall Software. It is now available under a modified BSD license, though formerly it was issued under the GNU General Public License. Either way, it remains free. It is listed as a bug tracking tool, but additionally known as open source and web-based project management software. It is mainly geared to those involved with software development programs.

For implementation, Trac uses the Python language. The only user interface option is Web for Trac.  SQLite, PostgreSQL and MySQL are all options for back end with Trac. Trac has currently upgraded to Genshi, an in-house template system, though it is expected to additionally be compatible with plugins from ClearSilver for some time to come.

In relation to source code revision control system integration, Trac has interface to Subversion built in. Other options available include Darcs, Bazaar, Mercurial, Perforce and Git. It will provide a web interface to any of those version control systems. Trac is integrated with Wiki documentation. Trac offers a plugin for test and planning integration. Reporting is both simple and convenient. Trac allows for information to be hyperlinked between a database, wiki content, and revision control.

Trac is amongst the bug tracking options to offer a customizable workflow selection. Unicode support is available with Trac. Trac offers a plugin for those requiring LDAP user authentication. It is supported by Unix, Linux, Windows and Mac OS X platforms. Amongst the well known worldwide users of Trac are Webkit and NASA's Jet Propulsion Laboratory.

Trac was first around in October 2006. This makes it one of the more recent issue tracking options. Trac was updated last in late June of the current year.   Further information concerning the features of the software and feedback can be obtained at http://trac.edgewall.org/

Considerations to be taken into account when comparing alternatives prior to opting on a choice for defect, issue or bug tracking software include the compatibility with your computer system, the performance and features of the proposed product, and the ease of interaction with the software. Matters that might also concern your choice might include the adaptability and personalization of the product, additional features such as compatibility with software development programs, or how data is viewed.

Defect tracking has great importance within the field of software engineering. There are generally thousands of defects appearing within a typical complex software system. These defects need to be evaluated, prioritized and managed. This can be a complicated task requiring adequate software analysis from a defect tracker to make it easier on the programmer. The better the chosen defect tracking software, the easier the task will be to manager the defects.

Issue tracking systems may also be called incident ticket systems or trouble ticket systems. Basically, they are a package of computer software designed to supervise and maintain inventories of issues. The customer support call center of an establishment will often utilize an issue tracking system. They can assist staff to deal with such matters as keeping track of a customer's complaint from initial contact through to its final resolution. Inter-employee problems may also be handled through this system.

The issue tracking system will usually contain a database of information concerning clientele as well as regular solutions and problems. The set up generally includes a main storage repository for all data. Further layers of the software program will be readable by staff members dealing with the data in various ways. A record of the issues, how they are dealt with and when, is all information that is stored in the database for future usage. In some systems, packages of information are dealt out to various employees in order to be dealt with directly from the core.

Many factors are taken into account when organizing the issues involved in the issue tracking program. They may be lodged in the order of the arrival of the report or the severity of the matter to be dealt with, which is usually the most important factor in a situation such as at a call center. Cases where there is no desperate pressure may be shifted in line behind those with more urgent features, for example. If a problem has not been solved in prior attempt, this may jump the queue to front of line if the software is programmed to do so.

A bug tracker is a software application program very similar to an issue tracking system. Many companies obtain software that will cover both matters at once. A bug is the unanticipated or unnecessary appearance of a feature affecting the running of a program or other development, generally contained within a source code. A bug tracker therefore locates and records data concerning these bugs for you to deal with in the future. Other possible features that many bug tracker programs have inbuilt are also available separately. These include static source code analyzers, debugging tools and API wrappers.

Similar to bug trackers are programs that scan in anticipation of possible bugs that may yet arise. These programs are termed static source code checkers or static source code analyzers. Debugging tools are the system for removal, relocation or deletion of the bugs that have been located by a bug tracker.

Another related feature that is sometimes included in a bug tracker is an API wrapper. An API wrapper will envelop calls to the structure libraries to enable you to inspect for suitable restrictions and disputes within the system calls.

Ensuring that you initially pick the correct software package to cover all the necessities of your company can save time and effort at a later date. It is therefore of advantage to contemplate the features available in depth, prior to deciding on which package might be right for you.



Bookmark and Share