Number of Seats/Users: Bugzilla offers discounts based on the number of users or seats. A higher volume typically leads to a better discount structure, especially for enterprise-level usage.

Commitment to a Long-Term Contract: Discounts are often provided to companies that commit to using the service for a longer period (e.g., 1-year or 3-year contracts). A longer commitment shows Bugzilla that the company is serious and willing to invest in the platform long-term.

No Active Discounts: Companies that are not already receiving other active discounts may have a better chance of qualifying for additional discounts from Bugzilla. Bugzilla reserves discounts for new customers or those not currently under promotional pricing.

Volume or Usage Commitment: Bugzilla offers discounts if you agree to a minimum amount of usage or transaction volume. This could be based on data storage, transactions, or other metrics tied to how much you will use the platform.

Enterprise-Level Negotiation: Companies that qualify as “enterprise” due to their size or complexity (e.g., having large teams, multiple departments, or geographical presence) may be eligible for additional discounts from Bugzilla. Such companies are often in a position to negotiate for better pricing.

Early Renewal or Prepayment: Bugzilla often offers discounts if you renew early or prepay for the entire contract period. This is a common approach to securing a lower price.

Here at Spendbase our internal data shows that Bugzilla is seen as a very strong value play: it covers core defect tracking needs at almost zero license cost, but it feels dated and limited compared to modern cloud suites.

From what our clients share, the main positives cluster around:

• Cost & licensing
• Open source / no license fees

• Attractive for startups, small teams, and budget‑conscious departments

• Core functionality

• Reliable bug logging and tracking
• Strong search and filtering (simple and advanced)
• Email notifications that work well and are timely
• Saved filters and customizable workflows for status tracking

• Time tracking, reports, and charts good enough for many teams

• Usability (for basics)

• Simple, no‑nonsense UI once you get used to it
• Very easy for engineers and testers to learn

• Can manage multiple projects and releases

• Customization (within limits)

• Good flexibility for bug workflows, fields, and automation
• APIs that integrate into internal automation and wrappers

On the downside, our internal data shows consistent friction in a few areas:

• User interface & UX
• Outdated look and feel; “from the 90s” is a common sentiment
• Too much scrolling, clumsy attachments, no thumbnails

• Themes and dashboard options are weak or missing

• Reporting & visibility

• Reporting and analytics often considered “not up to the mark”

• Lack of modern dashboards and at‑a‑glance views for managers

• Ecosystem & integrations

• Limited native integrations with popular tools (Git, agile suites, etc.)

• Primarily an isolated bug tracker, not a full agile or project platform

• Deployment & maintenance

• Often on‑prem, which means:
  • Extra admin/DevOps effort
  • Skills that are harder to hire
• Customization and initial setup can be non‑trivial

From a Spendbase savings perspective, Bugzilla tends to work best when:

• A team wants to minimize SaaS spend on tracking tools
• They already have in‑house resources to host and maintain it
• They only need a focused bug tracker, not a full agile suite

We often advise clients to balance the zero license cost against:

• Internal hosting and maintenance costs
• Productivity impact of dated UX and weaker reporting
• Any extra spend on complementary tools to cover missing features.