Comparison and Evaluation of Bugzilla, gnats and bugzero

Comparison and Evaluation of Bugzilla, gnats and bugzero

Websina/Excerpt one-eighth

This article briefly describes the differences between the bugzero defect tracking system and the other two popular open-source defect tracking systems, Bugzilla And gnats, in terms of installation, configuration, and customization, the purpose is to help you identify several issues you should consider before selecting a defect (Bug) management and tracking system.

Install

Bugzero(Cross-platform support based on Java/J2EE and databases ):

• Install Java (JDK 1.3 +)
• Install any database, including MySQL
• Install any J2EE or Servlet Engine
• Install bugzero (start setup Installation Wizard, Gui)

Anyone with some java/J2EE experience can use BugzeroIf you have a ready-made database and Servlet engine, the installation process will be faster.

Bugzilla(Based on Perl and MySQL databases, UNIX platforms/the latest support for Windows, open source code)

• Install MySQL database
• Install Perl 5.6.1 or later
• Install many Perl modules (command: Perl-mcpan-e 'Install "<modulename> "')

1. appconfig (1.52)
2. cgi (1, 2.93)
3. Data: dumper (any)
4. Date: Format (2.21)
5. DBI (1.38)
6. DBD: MySQL (2.9003) if using MySQL
7. DBD: PG (1.31) if using PostgreSQL
8. File: SPEC (0.84)
9. File: temp (any)
10. Templates (2.08)
11. Text: Wrap (2001.0131)
12. mail: mailer (1.67)
13. Mime: base64 (3.01)
14. Mime: Parser (5.406)
15. storable (any)

Available Perl modules:
1. Gd (1.20) (charts supported)
2. Chart: Base (1.0) (charts supported)
3. GD: Graph (any) (charts supported)
4. GD: Text: Align (any) (charts supported)
5. xml: Parser (any) (XML supported)
6. patchreader (0.9.4)
7. Image: magick (any) (convert image attachments to PNG format)

• Install Bugzilla (command: Perl-mcpan-e 'Install "Bundle: bugzilla "')
• Description of the reference Bugzilla Website:
  Someone with much Bugzilla experience can get you up and running in less than a day, and your Bugzilla install can run untended for years. if your Bugzilla strategy is critical to your business workflow, hire somebody with reasonable Unix or Perl skills to handle your process management and bug-tracking maintenance & customization.

If you do not have BugzillaImplementation experience and insufficient Perl skills, installation and configuration BugzillaIt will be a very time-consuming and laborious task.

Gnats(Based on C and file storage, only supports UNIX and open source code)

• Install gnatsd
• Configure gnatsd
• Install a GUI Front-End Interface
• Install some Perl modules

Configuration GnatsYou need to edit several configuration files in different locations.

Customization

To use Bugzilla, you may need to rewrite some source code to implement such operations as filling in custom fields, changing field data types, customizing drop-down menus, and configuring user access permissions. With bugzero, you can complete these tasks with just a few clicks.

Case 1:

Add or delete fields to customize the bug report table

Case 2:

Modify the priority of a field, for example, the priority of a "Priority" field.

Solution:

Bugzero: You can use web-based management tools without programming skills.
Bugzilla: In the user interface without adding or deleting fields, you must modify the relevant code to add or remove the option of a field, especially those that involve the bug handling progress. Obviously, custom Bugzilla requires some programming skills, especially Perl skills.

Availability

In Bugzilla, if you need to re-allocate a bug to another owner, you must enter the complete email address of the new owner instead of selecting from the owner drop-down menu, will this confuse you? Have you noticed that the attachment in Bugzilla does not have a file name and the file type is invisible, so that when you want to save the file, you must first understand what its extension is?

Bugzilla can only be sorted in one direction and cannot be sorted in reverse order. If you have multiple pre-stored query definitions and want them to have different display columns, it is a pity that this cannot be achieved because changing columns is global, all query definitions are affected.

BugzillaThese availability problems exist. Although the problem is not serious, it will always waste your time.

Process

Case 1:

Developers should not have the permission to mark the bug as 'verified 'or 'closed', they can only mark it as 'resolved/fixed/analyzed '. Only testers can use the 'closed/verified 'bug.

Case 2:

The successor status of a known bug should not be 'new'. Only the successor status of the status 'fixed' can be 'closed '; the status of 'Closed 'can only be 'reopened.

Solution:

Bugzero: Web-based management tools can be used to easily implement these status restrictions.
Bugzilla: You must modify the Perl code to meet the preceding requirements. In most cases, if you need process control, Bugzilla cannot meet your needs.
Gnats: Cannot be modified.

Security

Case 1:

The system has many users who come from many companies or organizations, and each company has several users. users from the same company should be able to see all the reports submitted by them, however, you cannot see reports submitted by other company users.

Case 2:

Your product has some bugs submitted by users, and developers have fixed them. Developers should enter the solution or process into the Bug Tracking System. This information is only shared by developers and does not need to be seen by your users.

Solution:

Bugzero: Case 1: You can grant 'group' permissions to the company user group. In Case 2, you can set a common user group as the forbidden access group of the "solution" field, so that the "solution" field is invisible to common users.
Bugzilla: No solution. Bugzilla is often used for the development and management of open-source software projects, and its security settings have limited flexibility.
Gnats: No solution.