MC Dashboards (Mission Control cross-board dashboards)
A workspace-scoped dashboard that pulls data from several Mission Control boards into one view: a drag-and-resize grid of widgets, a filter toolbar that scopes every widget at once, and export. Covers creating one, the widget types, and how board access is enforced.
On this page
What it is
A workspace-scoped dashboard that computes every widget client-side over the already-loaded board data, with a drag-and-resize grid, toolbar controls, and export. Part of Mission Control Phase 4d.
What it does
Create dashboards that aggregate data from multiple boards into a single view. Each dashboard is scoped to a workspace and isolated by account (a foreign board id in the config just 404s, never leaks data). Dashboards support several widget types: Numbers (abbreviated figures like $378k), Chart (bar / column / pie / donut / line), and three sprint-related widgets: Velocity, Planned-vs-unplanned, and Burndown (frontend-computed from configured sprint/effort/done/date columns; Velocity is faithful, the other two are documented approximations since there's no sprint-history backend). The Add widget menu also offers Battery (one bar split by status), Table (a compact item list) and Workload (who is overloaded, from a People column); Apps remains in code only. Every effort figure (Workload, Velocity, Planned-vs-unplanned, Burndown) uses the shared recipe in src/shared/pm-effort.ts: with no effort column each item counts 1; with one, a blank effort counts as 0, an entered 0 stays 0, a negative adds no work, and Workload splits a shared item evenly between its owners. When any counted item has a blank effort the widget shows one footnote line, "N not estimated, counted as 0".
Where to find it
Open Mission Control, then the Dashboards section in its left nav. From there the + button creates one and + Add widget builds it up.
How it behaves
How to use it
- Open Mission Control and click the "Dashboards" section in the left nav
- Click + to create a new dashboard
- Use the + Add widget dropdown to add widgets
- Connect boards via the N connected boards button (opens a connect-boards modal)
- Drag widgets to reposition, resize by dragging edges
- Use toolbar controls: People and Filter to scope widget data, Export to save as PNG or print-to-PDF
Key features
| Feature | Detail |
|---|---|
| Grid layout | react-grid-layout with per-widget {x,y,w,h} stored in config |
| Autosave | Draft + debounced-autosave model (no Edit/View toggle) |
| People/Filter toolbar | config.filters scope every widget's data via shared applyFilters; a rule only constrains boards that have its column |
| Export | Rasterizes the grid with html-to-image (PNG / print-to-PDF), or downloads connected-board data as CSV; each widget's ⋯ menu exports that widget the same three ways |
| Export failures | A failed export is always shown, never silent: a dashboard export reports in the page's error banner, a widget export in a dismissible toast. The message is the one exportDashboard.ts threw as an ExportError (for example "No project data to export"); any other error shows a generic "Couldn't export the dashboard" line and is logged, never shown raw (exportErrorMessage) |
| Invite | Reuses the member directory |
| Publish to Web | Dashboard header has a publish button (Phase 9b) |
| Deleted projects | A connected project that was deleted, archived or unshared puts a red warning icon on the N connected projects button; hovering it says how many. The connect window lists each one as a ticked Deleted or archived project row, so unticking it and pressing Done removes it. Nothing is removed automatically |
| Widget setup | A new widget opens on the first connected project that loaded, never on a deleted one. Its Project picker appears whenever there is more than one project or its own project could not be loaded, and an empty column picker says why. Chart and Battery start on the Status column, then Priority, then a Dropdown |
Data model
dashboards table (workspace-scoped + account-isolated like boards) with an opaque config JSONB (boardIds + widgets). CRUD goes over the Mission Control backend's /dashboards REST routes — the client in src/plugins/mission-control/web/features/dashboard/dashboardsApi.ts calls GET /dashboards?workspaceId=, POST /dashboards, and GET / PATCH / DELETE /dashboards/:id. The backend lives in Omniscio's own service, not in this tree. The DashboardPage computes every widget client-side over the existing ownership-checked GET /boards/:id/full.
Related
See also
- mission-control.md (parent page)
- INDEX.md
Last verified 2026-11-02