Currently, users can see what’s planned (Roadmap), requested (Feature Requests), and released (Changelog), but there’s no centralized place to understand what’s currently broken or degraded. A “Known Issues” tab would list active problems, their status (investigating, identified, fix in progress), severity, and any available workarounds.
Key Elements
Issue title and brief description
Status (Investigating, Identified, In Progress, Monitoring)
Severity/impact level
Affected features or versions
Workarounds (if available)
Links to related feature requests or fixes
Benefits
Improved transparency: Users can quickly understand if an issue they’re experiencing is already known
Reduced duplicate reports: Fewer repeated bug submissions
Better user trust: Proactive communication builds credibility
Faster troubleshooting: Users can find workarounds without contacting support
Clearer product narrative: Completes the loop. Users see what’s planned, shipped, and currently problematic
JAJoyce Akiko·2 months ago