About this block

Known Issues Board is a status list for confirmed problems. A page header pairs the title with a Subscribe to updates action, a row of status filter chips carries a count per state, and a card lists each issue with a status icon, a status badge, the reference, the affected area, a report count, and the last update time. The top issue expands to show a plain summary, a labeled workaround, an expected fix line, and a This affects me action, and a footer strip routes anything unlisted to the status page or a new report.

Issues and filters are two typed const arrays, and a statusMeta map pairs each state with its label and icon, so the board renders on the server with no client state. Leading with the workaround rather than the fix date is what keeps a blocked user moving while the real fix ships.

When to use

Reach for this block on a known issues or status route, wired to the tickets your team has already confirmed and triaged. Keep the reference, area, and report count honest so users can tell whether the issue they hit is the one you are tracking.

A natural flow around it on an Application Pro page:

Before

• Status health
• Help center home

After

• Contact support panel
• Submit request form

What you can display

One strong use is the public known issues board. Other configurations:

• Internal triage list. The same rows scoped to an on call or support team view.
• Incident recap. Resolved entries kept as a searchable history of what broke and when.
• Area status panel. Issues filtered to a single product surface on its settings page.

Tip: pair every open issue with a workaround before you publish it; a known issue with no path forward reads as an apology, not support.