Status Summary Table
Support queue with an Open, Blocked, and Done count strip above the ticket rows and a status badge per row.
Support queue with an Open, Blocked, and Done count strip above the ticket rows and a status badge per row.
Search blocks by description or jump to a page.
The source for every Application block is included with Basic and Pro. Pick a plan to copy the code.
Already purchased? Log in
Status Summary Table is the support queue view with a count strip docked above the table rows. The strip shows three inline chips: 12 Open, 4 Blocked, and 31 Done, so triagers can read the queue depth before scanning a single row. Below it eight tickets run from TKT-2026-0441, CSV export missing last row, down to TKT-2026-0414, Plan upgrade confirmation email arriving 30 minutes late. Each row carries a ticket ID in monospace, a truncated title, an avatar with assignee name, a status Badge, a timestamped created date, and an actions button.
The status-count strip and ticket rows are separate const arrays. The strip sits in a rounded-t-2xl panel joined flush to a rounded-b-2xl table so the border reads as one surface. Blocked tickets use the destructive badge variant to surface urgency without custom color tokens.
Reach for this block on any triage or queue page where workload distribution across statuses is the first question a team lead asks. Wire the count chips to your aggregate query and the rows to the paginated ticket list.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the customer support ticket queue. Other status-summary tables:
Tip: the count strip earns its space only when the numbers update in real time; a stale strip is worse than no strip because it quietly misleads.