6.4. Project Insights for Tracking Progress
A Project accumulates the same kind of activity data a repository does, and its own Insights view turns that into a picture of how work is actually moving.
💡 First Principle: Project insights chart how items move through a Project's fields over time — burnup and progress charts built from status field changes — so a team can see velocity and bottlenecks without manually counting cards on a board. Because the charts are generated from the same status fields driving the board or table view, they update automatically as items move, with no separate reporting step.
⚠️ Exam Trap: Project insight charts are generated from the Project's own status field history, not from repository-level Insights (3.4) — they answer "how is this specific initiative progressing," not "how healthy is this repository overall."
Reflection Question: A team's Project insights chart shows the "In Progress" column growing steadily while "Done" stays flat. What does that combination suggest about where the bottleneck likely is?
