What is Bugzilla
Introduction
Bugzilla is a robust, feature-rich, and mature defect-tracking system, also known as a bug-tracking system. It allows teams of developers to effectively keep track of outstanding bugs, problems, issues, enhancements, and other change requests in their products. While simple defect-tracking capabilities are often built into integrated source code management environments such as GitHub or other web-based or locally-installed equivalents, organizations may turn to Bugzilla when they outgrow the capabilities of those systems. For example, they may need workflow management, bug visibility control (security), or custom fields.
Design Principles
Bugzilla should remain focused on being a bug system during its development. Although there is potential to use the code to turn Bugzilla into a technical support ticket system, task management tool, or project management tool, we should concentrate on designing a system to track software defects. While developing the system, we should adhere to the following design principles:
- Bugzilla must run on freely available, open-source tools. While support for commercial databases, tools, and operating systems can be added, it should not be at the expense of open-source ones.
- Speed and efficiency should be maintained at all costs. One of the major attractions of Bugzilla is its lightweight implementation and speed. Calls into the database should be minimized whenever possible. HTML generation should not be a speed-sucking process, and only the necessary data should be fetched.
- All new queries and tables must use ANSI SQL calls and data types. Database-specific calls and data types should be avoided whenever possible, and existing SQL calls and data types should be converted to ANSI SQL.
- We should avoid browser-specific HTML and form generation, which means cleaning up the HTML output of Bugzilla and following all applicable standards.
Reference
https://www.bugzilla.org/