Why a chronology
Dashboards aggregate; sometimes you need the sequence. What happened on Tuesday afternoon when the incident started? What did the gateway team ship between the two releases? The Timeline answers by listing every event of the team, newest first, grouped by day, with the plain-language line and the effort score next to each commit.
Filters that compose
Filter by kind (commits, PRs opened, merges, reviews), by repository, and by contributor; filters combine. A “Select all” appears whenever not every contributor is selected, so a one-person view is one click away and one click back. The URL carries the filters, so a view can be shared with another manager.
Reading an event
A commit shows its one-line summary, repository, size and score. A pull request shows its title, author, requested reviewer and age; a merge shows who merged and after how many reviews. Clicking opens the event on GitHub in a new tab.
Performance
The timeline loads by day as you scroll, so a quarter of history on a busy team stays smooth. Non-working days are shaded and collapsed when empty.