Insights
The Insights tab gives you a single-screen view of where work is flowing through your team — across every project, status, and assignee. Use it to spot bottlenecks, see who's carrying the load, and decide what to plan next.
To open it: pick a team in the sidebar → click Insights → the Sankey Flow tab is the entry point.
Sankey Flow
The Sankey Flow chart is a three-column flow diagram:
┌─ PROJECTS ─────┬─ STATUSES ─┬─ ASSIGNEES ─┐
│ frontend │ done │ Alex │
│ backend │ inprogress │ Jordan │
│ ai-agent │ todo │ Priya │
│ voice │ inreview │ Unassigned │
└────────────────┴─────────────┴──────────────┘
Each ribbon connects a project to a status to an assignee. The thicker the ribbon, the more tasks it represents.
How to read the chart
- Column order is biggest at top. Within each column, nodes are sorted by total task volume — the project with the most tasks sits at the top of the projects column, and so on across statuses and assignees.
- Status colors are semantic — they always mean the same thing:
- 🟢 green =
done - 🟡 yellow =
inprogress - ⚪ grey =
todo - 🔵 blue =
inreview - 🔴 red =
cancelled - 🟠 orange =
blocked
- 🟢 green =
- Assignee color = their dominant status. A green assignee means most of their tasks are
done; a yellow one means they're mid-flight; a grey one means they're sitting on a pile oftodos. At a glance, the assignee column tells you who's shipping vs. who's stuck. - Project nodes are indigo (a single brand color — projects don't have a "status" of their own).
What hover does
Hover over any ribbon (project → status, or status → assignee). The chart:
- Highlights the full chain — the ribbon you're hovering plus every ribbon that shares an endpoint with it. So hovering "frontend → done" shows every assignee whose
donework came from frontend, AND every project whosedonework flowed out to those assignees. - Dims everything else.
- Pops up a card in the bottom-left of the chart with the source, target, flow type tag, and task count.
The two-tier highlight is intentional — the focal chain reads as one unit at the same brightness, instead of you trying to track three different opacity levels at once.
Three ways the Sankey helps day-to-day
1. "Who's behind on review?"
Look at the inreview (blue) ribbon flowing out of the status column. The thickest assignee on the receiving end is your review bottleneck. If one person owns most of the blue inflow, distribute reviews — or pair on the next batch.
2. "Are we shipping evenly across projects?"
Compare the green ribbons leaving each project. If frontend has a thick green band but backend is mostly yellow + grey, you're shipping frontend faster — backend may need a focused sprint.
3. "Did the sprint actually get done, or is it stuck?" A team that's mostly green in the assignee column is finishing work. A team that's mostly yellow or grey isn't shipping — and the chart tells you which assignees and which projects it's piling up in. Use it to plan the next sprint's scope honestly.
Filters
Use the Filters button in the toolbar to narrow what the Sankey shows:
- Project — focus on one or a few projects
- Sprint — see the flow for a specific sprint, not all-time
- Assignee — focus on one person's work
- Date range — created/updated within a window
Cancelled tasks are always excluded from the Sankey — they're dead work, not flow.
Other Insights tabs
The Insights page has additional tabs available alongside Sankey:
- Sprint Progress — burndown / completion across recent sprints
- Priority — task distribution by priority
- Explorer — interactive node-link graph for deeper exploration
- Treemap — area-encoded task counts
- Collaboration — who works with whom (chord diagram)
- Top Contributors — ranked task throughput
Each tab applies the same filters; switch between them for different angles on the same data.
Tips
- The chart is per-team, not per-project. Insights shows the whole team's flow regardless of which project you're inside when you click in.
- Numbers update on save. When you reassign a task or change its status, the chart reflects the new totals on the next page load. (There's a short cache window on the backend — refresh once if a recent change isn't visible yet.)
- Treat assignee colors as a planning signal, not a performance review. A grey assignee may simply be drowning in unblocked todo work that's nobody else's job to clear. Use the chart to start a conversation, not to score people.
- Pair the Sankey with Sprints. Sankey tells you the snapshot ("where is work right now"); the Sprint view tells you the trajectory ("are we burning down on time"). They answer different questions; use both.
For sprint-level tracking, see Sprints. For role and access setup, see Members & Roles.