Your First Dashboard
Once you’ve connected GitHub and added repositories, ProgressCue populates your home dashboard automatically. If you’ve just added repositories, you’ll see an import banner at the top — see Data Import for details.
Onboarding steps
Section titled “Onboarding steps”If your setup isn’t complete, the dashboard shows a “Get started in 3 steps” progress bar:
- Connect GitHub — links to Settings › Integrations › GitHub
- Add Repositories — links to Settings › Repositories › Manage (unlocks after step 1)
- Connect Slack — links to Settings › Integrations › Slack (unlocks after step 2)
Each step turns green with a checkmark as you complete it. The bar disappears once all three are done.
Account summary
Section titled “Account summary”The top bar shows three stat boxes:
- Members / Seats — tracked members vs total members (e.g. “5/10”), plus your plan’s seat limit
- Trial Days Left — remaining days in your trial period
- Repositories — count of tracked repos, with a + button that links to the Manage Repositories page
Current State
Section titled “Current State”The Current State section gives you a real-time snapshot of open pull requests across your organization. A green pulsing dot next to the heading indicates the data is live. Use the Team and Repository dropdowns to filter the view.
Four cards summarize what needs attention:
- In-Progress PRs — open PRs that are still being worked on
- Pending-Review PRs — PRs waiting for a reviewer
- Stale PRs — PRs open longer than your stale threshold, shown in the card label (e.g. ”> 7 days”)
- Large PRs — PRs exceeding your size thresholds, shown as a tooltip (e.g. ”> 400 lines or 10 files”)
The Stale PRs and Large PRs cards include a gear icon linking to Settings › PR Analysis where you can adjust the thresholds.
Click any card to expand a PR table underneath. Clicking the same card again collapses it. The table has seven columns:
| Column | Details |
|---|---|
| PR Title | Truncated title linking to the pull request on GitHub |
| Repository | Repository name |
| Author | Avatar and username linking to their People profile |
| Status | Color-coded badge — Draft (gray), In Progress (purple), Pending Review (blue), or Open (green) |
| Days Open | Number of days since the PR was opened |
| Lines | Total lines added and deleted |
| Files | Number of changed files |
Action Items
Section titled “Action Items”Below Current State, the Action Items carousel highlights issues that need attention. It shows one insight at a time — use the ← and → arrows to page through them. Each item has a colored icon and a message describing what was detected.
A View Detailed Metrics → link in the header takes you to the Metrics page.
If you haven’t connected any repositories yet, you’ll see “Connect your repositories to see bottlenecks and issues”. When everything is healthy, you’ll see “Nice! Everything looks good — no urgent action items right now.”
Insight types
Section titled “Insight types”ProgressCue generates the following insight types automatically:
| Insight | What it flags | Example message |
|---|---|---|
| Stale PRs | PRs past the stale threshold with no reviews or comments | ”PR #123 ‘Fix auth’ from @alice has been waiting 14 days with no reviews or comments” |
| Large PRs | Open PRs exceeding the lines-changed or files-changed threshold | ”PR #456 ‘Refactor API’ has 2300 lines changed across 15 files — consider splitting into smaller PRs” |
| Hotfix spike | Hotfix PRs this week ≥ 3 and ≥ 2.5× the 4-week average | ”5 hotfix PRs merged this week — normally you merge 2/week, might indicate stability issues” |
| Merge trend | Week-over-week change in merged PRs and average merge time | ”Great week! 24 PRs merged this week (up 30% from last week)” or “Average merge time increased to 3d 2h (was 1d 8h last week)“ |
| Inactive reviewers | Team members who haven’t reviewed any PRs in 7 days | ”@bob and @carol haven’t reviewed any PRs in 7 days — you might want to check their availability” |
| CI build waste | More than 10% of CI minutes lost to retries or failures | ”You spent 120 minutes on GitHub Actions builds. 35 minutes were due to retries/failures — ~29% lost to flakiness” |
Changelog
Section titled “Changelog”The right-hand Changelog panel lists recent ProgressCue product updates so you can see what’s new.