Tracking meaning over motion
Counting ticket updates tells you nothing about what got built. We just released the in-flight Tracker widget to show exactly what moved inside your repositories over a 24-hour window. 🚢
The new tracker provides an item-first view of what your team actually had underway. You get one clear row per piece of work. The system orders these by recent real activity and provides a plain language summary for each item.
Judging work by reality
We now judge status by meaning rather than by matching column names. Teams rename statuses freely. A backlog ticket is not in progress simply because someone dragged it to a new board.
Four distinct signals now qualify as active work. The system looks for tickets where the status means active development, open pull requests including drafts, items that landed inside the current window, and direct code pushes.
This update specifically uncovers hidden effort. Small teams often push code straight to a branch without opening a formal review. The platform now sees those direct pushes. Developers no longer read as idle on a day they shipped actual code. 🔎
Deep visibility into repositories
We expanded our core data sync to capture the full picture of repository activity. The platform reads side branches, commit files, review comments, and continuous integration jobs. Work pushed outside the standard flow is visible and accounted for. 📈
The system maps these repository signals back to your original tickets. This gives you a complete view of the work from planning through deployment. Our writing agents format every summary to read naturally, keeping the updates direct and clear.
Leaders need the truth about what their teams are building. You get that clear picture today, with zero new dashboards to learn.