40% OFF Annual Hosting Plans — Limited Time. Claim Now →
← Blog
Company News July 12, 2026 · 2 min read

Why Bug Reports Aren't a Public Board

When we built a dedicated way to report bugs — separate from general support, with its own status tracking and triage — the obvious comparison was our own Coming Soon board, which is deliberately public: anyone can see what's planned and how much demand there is for it.

Bug reports don't get the same treatment, and that was a deliberate choice, not an oversight. A feature request is, by nature, something you generally don't mind other people seeing — "I'd like X" isn't sensitive. A bug report is a different kind of content entirely. It often includes exactly what a customer was doing when something broke, which can touch account-specific detail, and occasionally something closer to a security concern than a cosmetic annoyance.

Showing every user's raw bug reports to every other user would mean exposing that detail broadly for the sake of transparency that isn't actually the point of a bug tracker in the first place — the point is that something gets fixed, not that everyone gets to watch how.

So reporting a bug requires an account, reports are visible only to the person who filed them and to our team, and status updates happen in a private thread rather than a public timeline. Real accountability doesn't require a public audience — it requires that the report goes somewhere, gets triaged, and the person who filed it can actually see it get resolved.
#bug-reports #product #privacy

More Company News

How We Decide What Goes on the Coming Soon List

Opening the ACBIZ Marketplace to Outside Vendors

Why We Built a Public Status Page