Bugzilla is a powerful and mature defect tracking system (or error tracking system). The defect tracking system allows the team of developers to effectively track unresolved defects, problems, issues, enhancements, and other change requests in the product. Simple defect tracking is usually built into Github or other integrated source code management environments based on network or local installation.
Bugzilla is a web-based system, but it needs to be installed on your server to use it. However, the installation is not complicated.
Bugzilla development should focus on becoming a bug system. Although there is potential in the code to transform Bugzilla into a technical support ticket system, task management tool or project management tool, the development team focuses on the task of designing a system to track software defects. In the development process, the following design principles shall be followed:
- Bugzilla must run on free open source tools. Bugzilla support should be extended to support commercial databases, tools and operating systems, but not at the expense of open source databases, tools and operating systems.
- Speed and efficiency should be maintained at all costs. One of the main attractions of Bugzilla is its lightweight implementation and speed. Try to reduce calls to the database as much as possible, do not generate slow HTML, do not get more data than you need, and so on.
- ANSI SQL calls and data types must be used in all new queries and tables. Avoid database specific calls and data types as much as possible. Existing SQL calls and data types should be converted to ANSI SQL.
- The HTML and form generation should be browser independent, which means cleaning up the HTML output of Bugzilla and following all applicable standards.
