Bugzilla vs Buildtable

Bugzilla is a self-hosted, web-based system for tracking defects, issues, enhancements, and other product change requests. It is free and open source, and runs on Linux, macOS, and Windows, with API access. Its search ranges from full-text queries to advanced searches, including time-based criteria. Users can choose which bug-change emails they receive, and scheduled search reports can be sent as often as every fifteen minutes. Reports can include tables and graphs, and can be exported as CSV. Administrators can tailor workflows, statuses, resolutions, and fields, then extend an installation with templates and extensions. Groups control who can view or edit bugs; an insider group can make comments and attachments private. Bugzilla supports XML-RPC and JSON-RPC services, several authentication methods, and MySQL, PostgreSQL, or Oracle databases. Its Patch Viewer connects with LXR, CVS, and Bonsai. Support is community-based through mailing lists and chat rooms; the project does not directly provide commercial support.

Buildtable is a web workspace for indie game studios covering bug tracking, release management, initiatives and playtesting. Its Bug Center combines a public submission portal with a kanban workflow; players can send reports without an account, and teams can tag them by priority and source. Versioning tracks releases and patches and connects resolved bugs to releases. Initiatives organize features, patches and overhauls into milestones and track progress. Other modules include Playtesting, Tasks, Localization, Public Roadmap and Canvas. Buildtable says it works with Unity, Unreal, Godot, GameMaker and custom engines. Its service also includes localization management and team collaboration. The free-forever plan costs nothing, covers one game and two team members, and includes Bug Center and Tasks without requiring a card. Users retain ownership of content and data they upload or create, and Buildtable says it does not use user data to train AI models. Telemetry and SDK log events are deleted seven days after collection. The cloud service is provided on a best-effort basis without guaranteed uptime, availability, performance or service-level agreements.