The Ito dashboard gives you an overview of QA activity across your connected repositories. It shows aggregate statistics, a filterable list of pull requests, and detailed per-PR test results.
Statistics overview
At the top of the dashboard, a statistics card summarises QA activity for the selected time period.
Period selector
Use the period dropdown to scope the statistics to Last 7 Days, Last 30 Days, Last 90 Days, or All Time.
Severity cards
The statistics card shows bug counts broken down by severity:
| Severity | Description |
|---|
| Critical | Severe issues that block core functionality or break key user flows |
| High | Major issues that impact important features or significantly degrade the user experience |
| Medium | Noticeable issues that affect usability but don’t block core functionality |
| Low | Edge cases or cosmetic issues with limited impact |
Summary metrics
- PRs Tested — total number of pull requests Ito has run tests on within the selected period
- Bug Detection Rate — percentage of tested PRs where Ito detected at least one issue; shown alongside the count of PRs with bugs vs. total PRs tested
Donut chart
When bugs have been found, a donut chart shows the proportional breakdown of bugs by severity level.
PR list
Below the statistics, a table lists all pull requests Ito has processed. Each row shows:
- Pull Request — title, PR number, repository name, and author
- Opened — how long ago the PR was opened (hover to see the exact date)
- Tested — how long ago the last test run completed
- PR Status — the current state of the pull request on GitHub (open, closed, merged)
- Test Results — pass/fail counts for the latest test run; a spinning indicator means tests are still running
Filtering the list
Use the filter controls above the table to narrow the list:
- State — filter by PR status (open, closed, merged)
- Author — filter by the GitHub username of the PR author
- Repository — filter to a specific connected repository
- Period — filter to PRs opened within the selected time window
PR detail view
Click any row in the PR list to open the detail view for that pull request.
The header shows the PR title, number, repository, author, and a link to open the PR on GitHub.
Split-panel layout
The detail view uses a split panel. You can drag the divider to resize the panels.
- Left panel — list of all test cases for this PR
- Right panel — details for the selected test case
Test case list
The left panel groups test cases by status using tabs:
- All Test Cases — every test case from the run
- Passed (check icon + count) — test cases that passed
- Failed (× icon + count, shown in red) — test cases that failed due to issues introduced by this PR
- Additional findings (info icon + count) — pre-existing failures unrelated to this PR, shown with the highest severity color
Each test case in the list shows its name, severity emoji (for failures), and category tag. Click a test case to open its details in the right panel.
Test case details
The right panel shows full details for the selected test case.
Video recording
If a screen recording is available, a video player appears at the top of the right panel. Ito automatically seeks the video to the timestamp of the failure — you can scrub backwards to see what led up to it.
If the video starts at the point of failure, scrub backwards a few seconds to see the steps that preceded it. This often reveals the root cause faster than reading the reproduction steps alone.
Reproduction steps
Expand Reproduction Steps to see the numbered sequence of actions Ito took before the failure occurred.
Stub / mock context
Expand Stub / mock context to see any mock data or stub configuration that was active during the test run.
Code analysis
Expand Code Analysis to see Ito’s analysis of the relevant code, including file paths, line ranges, and code snippets from the diff that relate to the failure. 