Bugzilla is written in Perl and typically runs on Linux/Unix servers, though it can also work on Windows.
Bugzilla supports the following databases :
It's recommended to use MariaDB, MySQL, or PostgreSQL for production environments. Oracle is supported, but it's not as extensively tested. SQLite is suitable only for testing or very small installations due to its limitations.
| Aspect | Priority | Severity |
|---|---|---|
| Definition | Defines how quickly the bug should be fixed. | Defines how serious the impact of the bug is. |
| Levels | P1 (Highest) to P5 (Lowest) | Blocker, Critical, Major, Minor, Trivial |
| Who Sets It? | Project Manager, Team Lead | Tester or Developer |
| Example | A minor UI issue in a high-profile release = High Priority | A crash causing data loss = Critical Severity |
Yes, you can customize fields in Bugzilla. Bugzilla has a feature that allows administrators to add custom fields to bugs, which can be used to capture additional information specific to your project or organization.
To add a custom field, you need to log in to Bugzilla as an administrator and go to the "Custom Fields" link in the footer of the page. From there, you can add a new field, specifying its name, description, type, and other attributes.
There are several types of custom fields available, including:
Once you have created a custom field, it can be used like any other field in Bugzilla. You can set its value when creating or editing a bug, and you can use it to search for bugs.
In addition to custom fields, Bugzilla also allows you to customize other aspects of the bug tracking system, such as the workflow, email notifications, and user permissions.
Bugzilla offers several ways to search for bugs, catering to different levels of information you have about the bug:
1. Quick Search:
2. Simple Search:
3. Advanced Search:
4. Custom Search:
Tips for Effective Searching :
Remember that Bugzilla's search functionality might have some specific syntax or features depending on the version and configuration. You can usually find more detailed information about searching in the Bugzilla documentation or help resources.
In Bugzilla, a Watchlist is a feature that allows you to track the emails another Bugzilla user receives. This can be useful in situations like:
How it works:
How to use it:
Important Notes:
By using the Watchlist feature, you can effectively monitor bug-related activity and ensure that you stay informed about important updates and discussions.
Bugzilla can be integrated with other tools in a variety of ways, allowing you to streamline workflows, improve communication, and enhance your overall development process. Here are some common integration methods:
1. API Integration:
2. Email Integration:
3. Third-Party Integrations:
4. Webhooks:
5. Custom Integrations:
Benefits of Integration:
Bugzilla has a robust system for managing email notifications, allowing you to fine-tune what events trigger emails and who receives them. Here's a breakdown of how to set up email notifications:
1. Accessing Email Preferences:
2. Global Options:
3. Specific Event Notifications:
4. "User Watching" Feature:
5. Ignoring Specific Bugs:
6. Saving Changes:
Important Considerations :
By carefully configuring your email preferences in Bugzilla, you can ensure that you stay informed about the bugs that are most relevant to you without being overwhelmed by unnecessary notifications.
In Bugzilla, a Component is a subcategory within a Product that helps to further organize and classify bugs. Think of it as a way to divide a product into its different parts or modules.
Here's a breakdown of what Components are and why they're useful:
Purpose of Components:
Example:
Imagine you have a "Web Application" product in Bugzilla. You might divide it into components like:
How Components are Used:
Key Features of Components:
Bugzilla has different user roles and permissions, such as :
Bugzilla has built-in mechanisms to detect and handle duplicate bugs efficiently. Here’s how it works :
