Should I publish a known issues page?

Yes, a known issues page is worth publishing, because it reassures players that you are aware of problems, deflects support tickets and duplicate reports, and builds trust through transparency, for very little effort. A known issues page lists the problems you know about, so players who hit one see it is acknowledged (reducing the frustration of feeling ignored) and do not file a ticket about it (deflecting support volume and duplicate reports). It also signals transparency and responsiveness, which builds trust. The key is keeping it current, listing the issues you actually know about and removing them as fixed, since a stale page erodes trust. It is most valuable at launch and in live games, when issues surface and players want to know you are aware. Bugnet captures the real issues players hit (so you know what to list) and provides a public tracker you can keep current, so you can publish a known issues page that reassures players and deflects support tickets, addressing player frustration and support volume for very little effort, which makes a known issues page well worth publishing.

What's the difference between a known issues page and a bug tracker?

A known issues page is a simple list of problems you are aware of (for players to check), while a public bug tracker is a more detailed, often interactive view of issues with status and progress, the known issues page is the lighter-weight version. Both serve the same purposes (reassuring players, deflecting tickets, building trust through transparency), but a known issues page is typically a simpler static list of current problems, while a public bug tracker shows more, the status of each issue, your progress, and resolution. You can start with a known issues page (low effort) and grow into a fuller public tracker as needed. Both should be kept current and honest. Bugnet provides a public tracker that can serve as either, a simple known issues list or a fuller tracker with status and progress, so you can show players the issues you are aware of and your progress at whatever level of detail suits your game, with the captured issues feeding it automatically, so you can offer the reassurance and deflection of a known issues page (or a fuller tracker) without much effort.

How do I decide what to put on a known issues page?

List the real, current issues that affect players, especially the high-impact ones many players hit, based on your captured crash and bug data, and remove issues as they are fixed. A known issues page should reflect reality: the actual problems players are hitting (so it reassures them and deflects tickets), prioritized toward the high-impact ones (the issues affecting the most players, which generate the most frustration and tickets). Use your captured data to know what is actually affecting players, rather than guessing. Keep it current by removing issues as you fix them (and noting fixes via a changelog). Avoid listing trivial issues that clutter the page or omitting real ones that players are hitting. Bugnet captures crashes and bugs from the field with impact ranking, so you can see the real, high-impact issues players are hitting (including the silent majority's) and list those on your known issues page, keeping it accurate and current as you fix issues, so the page reflects what actually affects players and provides genuine reassurance and deflection rather than a stale or incomplete list.

Do You Need a Known Issues Page?

Quick answer: Yes, a known issues page is worth having, it reassures players you are aware of problems, deflects support tickets, and builds trust, for little effort.

A known issues page is one of the simplest, highest-value things you can publish. Here is whether you need a known issues page.

Why You Need It: Reassurance and Deflection

A known issues page reassures players that you are aware of the problems they hit (so they do not feel ignored), deflects support tickets and duplicate reports (players see the issue is known rather than filing one), and shows transparency (which builds trust). For very little effort, it addresses a lot of player frustration and support volume.

Bugnet captures the real issues players hit (so you know what to list) and provides a public tracker, so you can show players the known issues and reduce the tickets and frustration that come from players not knowing whether you are aware.

The Key: Keep It Current

A known issues page is only useful if it is current, listing the issues you actually know about and removing them as they are fixed. A stale page that lists fixed issues or omits real ones erodes trust, while a current one that reflects reality reassures players and deflects tickets.

Bugnet's tracker lets you keep the known issues current and mark them resolved (with the changelog showing the fix), so your known issues page reflects reality rather than going stale.

When You Need It Most: Launch and Live Games

A known issues page matters most at launch (when issues surface at scale and players want to know you are aware) and throughout a live game (when new issues arise). At these times, a current known issues page prevents a flood of duplicate reports and reassures players that you are on top of things.

Bugnet's tracker is built for ongoing visibility, so at launch and in live operation you can keep a current known issues page that reassures players and deflects the support volume that otherwise spikes.

Yes, a known issues page is worth having, it reassures players you're aware of problems, deflects support tickets, and builds trust, for little effort, as long as you keep it current.