Quick answer: Keep all known issues in one place with status (open, in progress, fixed) and context, fed automatically from crashes and reports so nothing is lost.
Known issues scattered across your memory, Discord, and email are issues half-lost. Keeping track of them well, in one organized place, is the foundation of actually fixing them. Here's how to maintain a known-issues list that stays useful instead of becoming a graveyard.
Keep Everything in One Place
The foundational habit is a single place every known issue lives, rather than scattered across channels and your memory. When all issues are in one list, fed automatically from crashes and player reports, nothing falls through the gaps, and you always know where to look.
Bugnet gives you one place that crashes and reports flow into automatically, so known issues are captured without effort. A single source of truth is what keeps issues from getting lost, which is the most common way known issues stop being tracked at all.
Track Status and Context
A known-issues list is useful only if each item carries enough to act on: its status (open, in progress, fixed) so you know what's been done, and context (device, version, what happens) so it's still actionable when you get to it. An item logged as just 'menu broken' isn't trackable.
Bugnet tracks status and attaches context to every issue, with an activity history, so each known issue stays actionable and you can see what's been tried. Status and context are what keep a known-issues list a working tool rather than a pile of vague notes.
Group and Rank So the List Stays Meaningful
A known-issues list bloated with duplicates and unranked is hard to use. Grouping duplicates keeps the list reflecting distinct problems, and ranking by impact keeps the ones that matter at the top, so the list stays a meaningful, prioritized view rather than an overwhelming pile.
Bugnet groups duplicates and ranks by affected players automatically, so your known-issues list reflects real, prioritized problems. Keeping track of known issues is one place, status and context, and grouping and ranking, the combination that keeps the list useful as it grows.
Keep all known issues in one place with status and context, fed automatically so nothing is lost, then group duplicates and rank by impact so the list stays a meaningful, prioritized tool.