Dashboards

The Dashboards view is a single read-only analytics surface that aggregates issues, projects, users, and activity into the chart panels you’d build by hand in a BI tool. Open it from the rail under Plan → Dashboards. There are no CRUD operations — the panels are fixed and the data comes straight from the existing platform endpoints.

What’s shown

Top-line metrics (4 cards)

Card	Computation
Total Tasks	Issue count for the active team scope, annotated with the count in backlog or todo
Completed	status = done count + completion-rate % (done / total)
In Progress	status = in_progress count
Projects	Project count in scope, with a “X completed” annotation (projects with 100% issue completion)

Charts

Panel	Source data	Lookback
Issue Throughput	Two area series: Created (issues by createdAt) and Completed (status-change activities to done)	Last 30 days
Status Distribution	Donut over the active set; centered % is the same done / total ratio as the metric card	Current snapshot
Weekly Velocity	Side-by-side bars per ISO week — Created vs Completed	Last 8 weeks
Priority Breakdown	Donut of issues bucketed by priority (none / low / medium / high / urgent)	Current snapshot
Project Progress	Per-project bar — issue completion % per project, sorted by total issues	Current snapshot
Team	Per-user list — total issues assigned and number done, sorted by completed count	Current snapshot
Recent Activity	The 6 most-recently-updated issues in scope	—

Team scoping

The dashboard inherits the global team picker from the sidebar:

• No team selected — counts and charts span the entire org.
• Team selected — every panel is filtered to issues + projects whose teamId matches.

Switching the team picker re-renders all panels client-side; nothing is persisted server-side. There’s no per-user “save this view” affordance — it’s deliberately a single canonical dashboard.

Data flow

GET /api/v1/issues       (all org issues)
GET /api/v1/projects     (all org projects)
GET /api/v1/users        (org members)
GET /api/v1/activities?limit=500   (status-change activities for throughput/velocity)

The page fetches all four in parallel on mount, filters client-side by currentTeam.id, and re-derives the chart datasets via useMemo. Refreshing the page re-fetches; there is no auto-poll today.

What it is not

• Not customizable. Panels are hardcoded; there’s no “add widget” UI or saved-view mechanism. If you want a slice the panels don’t expose, build it in Custom Views on the issue list, or query the API directly.
• Not real-time. The dashboard is a snapshot at page load — it doesn’t subscribe to updates over the inbox SSE channel.
• Not exported. There’s no PDF/CSV export today; for shareable artifacts, screenshot the panels or query the underlying endpoints and produce your own report.

See also