Skip to content

Insights and views

Insights

A workspace's review speed, build outcomes, flaky screenshots, failures and storage over 7, 30 or 90 days.

Insights answers "how is review going?" for a workspace: how long builds wait, how they end, how many screenshots are flaky, what fails, and what is stored. Open it from the sidebar, under the workspace's name. Any member of the workspace can see it.

CirCI
The Insights page of the Acme workspace on the 30 days range. Six summary tiles, such as a median time to first review of 18 hours and 66 percent of first reviews within target, then the first trend charts, a bar chart of median time to first review per week and a line chart of time to decision.
The summary tiles and the first two charts, over 30 days. Each tile says how it compares with the 30 days before.

Two controls sit in the page header:

  • Project: all projects, or one. The choice is kept in the address, so a link shows the same view.
  • Time range: 7, 30 or 90 days. The default is 30.

With nothing built or reviewed in the range, the page says "No data yet" and suggests a longer range.

Charts use one bar per week, or one per day in a 7-day range. Weeks run Monday to Sunday, UTC.

Six tiles open the page. Each has its value, a note, and how it compares with the same number of days before (for example "vs the 30 days before"), marked better or worse where that has a meaning.

Tile Shown as What it measures
Median time to first review Minutes, hours or days (18h) From a build being ready to the first approval or rejection by a person (automatic approvals don't count), with the slowest 10% in the note
Median time to decision Minutes, hours or days From the build being ready to it being approved or rejected, with the slowest 10%
First reviews within target Percent The share of reviews that came within the project's review target, weekends not counted. "No review target set" when there is none. See Review requests and rules
Builds reviewed Builds How many builds got a review in the range
Builds with changes Percent The share of finished builds that had changes, with the count in the note
Failed builds Builds How many failed, with their share of finished builds in the note
  • Median time to first review, in hours, per week or day.
  • Time to decision: the median and the slowest 10% as two lines, in hours.
  • Outcomes: finished builds per period, stacked as Approved, Auto-approved, Rejected and Failed.
  • Waiting for review: builds waiting at the end of each day.
  • Flaky screenshots at the end of each period, Failed builds per period and Processing time (median and slowest 10%, in minutes). See Triage and flaky screenshots.

Hover a bar or point for its exact numbers.

  • Projects: a table with builds, how many had changes, review time, flaky and failed counts for each project.
  • Why builds failed: failed builds grouped by error message, most common first.
  • Rejection reasons: how many builds were rejected and how many came with a reason, with the reasons listed.
  • Ignore regions: how many screenshots would have changed without them, and which regions suppressed the most. See Baselines and ignore regions.
  • Storage by project: screenshots, diffs and baselines, with the total. A note says how long retention keeps branch builds; see Workspace settings.
  • Reviewer load: for each person, how many reviews, how many requests are open, their median response time and how many were overdue.

Four tables point at specific things:

  • Most changed screenshots: the ones that changed in the most builds, with how many of the last 10 default-branch commits changed them.
  • Flakiest screenshots: flip-flops in the last 10 commits on the default branch.
  • Oldest waiting builds: builds still waiting for review, longest first, with branch, author and wait time.
  • Rejected most often: screenshots rejected most in the range.

Every table sorts when you click a column header. The sort is kept in the page's address, so you can share a sorted view.