Insights
Insights answers the questions status meetings exist for, without the meeting. It’s one page of plain counts, and every number opens the exact issues behind it. Numbers. No spin.
Before you start
Section titled “Before you start”- Anyone in the workspace can open Insights. It’s read-only, so there’s nothing to break. Who can do what.
- Insights uses the workspace’s planning timezone for weeks and dates. Until an Admin confirms one under Settings › Planning calendar, it uses UTC and says so. See Confirm the planning calendar.
- The Cycles section and the Current cycle window need cycles turned on. Everything else works without them.
Set the scope
Section titled “Set the scope”Open Insights in the sidebar. Two pickers at the top scope everything above the Cycles section:
- Window: Last 4 weeks (default), Last 12 weeks or Current cycle.
- Who: Everyone, one person or agent, or Unassigned.
The line underneath shows the dates, the timezone and when the numbers were taken. The page refreshes itself every minute while you’re looking at it.
Read the tiles
Section titled “Read the tiles”Four tiles, each a count you can click for the list of issues:
| Tile | Counts |
|---|---|
| In progress | Issues in progress right now, and how many people, agents or nobody hold them. |
| Waiting for review | Issues in a review stage right now, and how many have waited over 3 days. |
| Blocked | Open issues with a direct blocker that isn’t Done or Canceled, and how many blockers. |
| Delivered | Issues that reached Done in the window, how many were captured, and whether the backlog grew, shrank or held. |
The first three are right now. Delivered is the window. Parent issues that group sub-issues are never counted in the tiles.
Clear the Needs a decision list
Section titled “Clear the Needs a decision list”Needs a decision lists issues that have been in a review stage for more than 3 days, and open issues that are holding up other work, oldest first. When it’s empty: “Nothing is waiting on you. Enjoy it; it won’t last.”
See who’s holding what
Section titled “See who’s holding what”Who’s holding what has one row per assignee: how many issues they have in progress, in review, ready and blocked. The Unassigned row shows what’s ready and in the backlog with nobody on it. Open as issue list takes you to the same work as a list.
It’s issue counts, not hours. There’s no ranking, no score and no leaderboard. It shows where the work is sitting, not who’s winning.
Read In versus out
Section titled “Read In versus out”In versus out compares issues captured with issues delivered, week by week, as paired bars. Weeks start on Monday. Beside the chart:
- N in, N out, and which way it’s going, with a streak when it’s lasted two weeks or more. Both numbers open their issues.
- Delivered per week, averaged over the complete weeks in the window. The current week is “so far” and never drags the rate down.
- Median from capture to Done: calendar days from creation to first Done, across the issues delivered in the window, with how many that is.
The chart waits for 2 complete weeks of history rather than drawing a line through one dot. Same numbers as a table is there if you’d rather not read bars.
Read the Cycles section
Section titled “Read the Cycles section”With cycles on, the bottom section shows:
- Velocity: the range of issues delivered per closed working cycle, over the last closed cycles, with how many that is. “A range, not a forecast.”
- The running cycle’s burnup. See Cycles.
- A table of each cycle’s Committed, Delivered (with anything added mid-cycle) and Carried over, plus the running cycle so far.
This section covers the whole workspace on each cycle’s own dates. Who and Window don’t apply down here.
Check the rules
Section titled “Check the rules”How it’s counted, in the line under the heading, opens the exact definitions. The same rules apply in the app and for agents over MCP.
What you should see
Section titled “What you should see”A page you can take in at a glance. If the workspace uses sizes, size points appear beside the counts: on the tiles, per assignee, in the per-week rate and in the cycles table. Unsized issues are left out of every sum and counted beside it. T-shirt sizes count XS 1 to XXL 6; Fibonacci sizes count as their own number. Sizes are ordinal, so a sum is a hint, not a measurement. See Labels, sizes and priority.
What Insights deliberately doesn’t do: forecast, estimate capacity, rank people or compare them against each other. If you want a burndown to wave at stakeholders, this isn’t the place.
If it goes sideways
Section titled “If it goes sideways”- “(no workspace timezone yet; confirm one in Settings › Planning calendar)” Weeks and dates are in UTC until an Admin confirms the planning calendar under Settings › Planning calendar.
- Current cycle is greyed out. Cycles are off. An Admin can turn them on in Settings › Cycles.
- The In versus out chart is empty. It needs 2 complete weeks of history. Come back next week.
- Delivered is lower than you expected. Delivered counts an issue’s first move to Done inside the window. Reopening and finishing again doesn’t count twice, and an issue created already Done or Canceled isn’t delivered.
- A person’s delivered count looks off. Delivered credits whoever held the issue when it reached Done. The right-now counts use the current assignee.
- No points anywhere. The workspace’s sizing is Off, or no issue has a size yet. A cycle that closed before sizes were recorded shows none.
- “The refresh didn’t come back.” You’re seeing the last snapshot; nothing was replaced with a zero. Click Retry, or check status.hydrant.dev (opens in a new tab).