In this guide
A known issues list tells testers what you already know, so they spend their time on things you do not. It cuts duplicate reports and makes clear which problems are accepted for this build and which are not.
Copy-paste template
KNOWN ISSUES: [App name], build [version / build number], [date]
Already known, no need to report:
1. [Short title] - [Where it happens]. Workaround: [workaround or "none"]. Status: [will fix in build X / accepted for now].
2. ...
Not ready yet, please skip:
- [Screen or feature] - [one line why]
Still report:
- Anything that crashes or loses data, even in an area listed above.
- A known issue that behaves differently than described here.
How to report: [link or channel]. Please include device, OS version and steps.
Example (invented)
KNOWN ISSUES: Pocket Budget, build 0.9.3 (42), 2026-10-17
Already known, no need to report:
1. Dark mode: chart labels are hard to read on the Stats screen. Workaround: use light mode. Status: will fix in the next build.
2. CSV export is slow with more than a few hundred entries. Workaround: none. Status: accepted for now.
Not ready yet, please skip:
- Settings > Backup - not wired up yet
Still report:
- Anything that crashes or loses data, even in an area listed above.
- A known issue that behaves differently than described here.
How to report: reply to this message. Please include device, OS version and steps.
How to adapt it
- Keep it short. If the list has more than about ten items, testers stop reading it. Remove fixed items with every build.
- Name the build. A list without a build number is wrong one release later.
- Describe symptoms, not causes. Testers match what they see, not your internal ticket names.
- Keep the "still report" lines. Otherwise testers assume a listed area is off limits, and you miss new crashes there.
- Do not hide serious problems. A known data-loss bug belongs in the list, with a warning, not in silence.
- Use it with the build. Send the list in the same message that hands out the build, and link it from your release notes.
Related: release go / no-go checklist, hotfix checklist, and the hub mobile app testing checklists.
Want testers who report in a structured way? Start free.