Follow one bug.

Issue #1400 is a refund that pays out twice. Follow it through Turnstone in five short films. Each one widens the view, from one bug to the facts Turnstone keeps.

Sample dataEvery screen is the real Turnstone dashboard, showing Acme, a fictitious organisation.

5 films

1One bug

Meet #1400.

Here is the refund that pays out twice, from the commit that brought it in to the fix.

One bug, start to finish
More on Meet #1400. Notes, chapters, and the transcript

Commit 42c7079 brought it in on 14 Apr. A campaign caught it on 30 Jul, 107 days later, and commit a47fc8a fixed it on 16 Aug.

The report stays in the GitHub issue, and the failing test stays in the repository.

  1. Lifetime
  2. The issue

Descriptive transcript

Sample bug #1400, shown in Turnstone's dashboard with sample data for Acme, a fictitious organisation. It was introduced on 14 April 2026 in commit 42c7079.

It hid for 107 days. Hidden time is reconstructed from the recorded introduced and caught dates.

A campaign caught it on 30 July 2026.

It was fixed 17 days later, on 16 August, in commit a47fc8a.

The report, the failing test, and the evidence stay in the GitHub issue. Turnstone links to it and keeps only the facts.

Turnstone is at turnstone.cloud.

2One day

It wasn't alone.

Pin 30 Jul, the day #1400 was caught, and see what else was in Shop's code.

Rewind to any day
More on It wasn't alone. Notes, chapters, and the transcript

The reconstructed view puts 59 bugs in Shop's code on that day, including #1400.

Turnstone rebuilds each day from the dates on bugs that were caught later. It can't show a bug nobody has found.

  1. Bugs in the code
  2. Pin a day

Descriptive transcript

Turnstone can rewind its bugs-in-the-code chart to any day. This is the real dashboard with sample data for Acme, a fictitious organisation.

Scrubbing the chart previews each day: how many recorded bugs were hiding in the code, caught and waiting, or fixed.

Pinning 30 July 2026, the day a campaign caught sample bug #1400, lists every bug in the code that day. #1400 was still hiding then.

On 30 July, 59 bugs were hiding in the Shop project's code. The chart is rebuilt from bugs that were later caught and dated, so it cannot show bugs nobody has found.

Turnstone is at turnstone.cloud.

3One area

Bugs gather.

Is #1400 a one-off, or part of a pattern in Checkout?

Find where bugs gather
More on Bugs gather. Notes, chapters, and the transcript

Over the last 6 months, Checkout holds 45% of Shop's bugs in 16% of its code. #1400's cause, Null or default mishandling, accounts for 11 of those Checkout bugs, and #1400 is one of them.

These counts show where bugs were recorded. They don't measure a defect rate, and they say nothing about who wrote the code.

  1. Bugs by area
  2. Cause by area
  3. The bugs behind it

Descriptive transcript

Bugs by area stands each area's tower on its share of the code. In this sample, Checkout holds 45% of the recorded bugs in 16% of the code. That is a concentration of recorded bugs, not a defect rate or a cause.

The cause-by-area matrix counts the bugs that share both facts. In the last 6 months, Checkout with null or default mishandling, #1400's cause, has 11 bugs. Missing validation ties it.

Selecting the cell lists those 11 bugs. Sample bug #1400 is one of them. Each row links to its issue in GitHub, where the report and its regression test live.

Turnstone is at turnstone.cloud.

4Over time

Some hide for months.

#1400 hid for 107 days. Was that unusual?

What hid the longest
More on Some hide for months. Notes, chapters, and the transcript

Over the last 6 months, 32 of Shop's bugs hid for more than 90 days, #1400 among them.

Hidden time runs from the commit that brought a bug in to the day someone caught it. Bugs with no recorded introduction date are left out.

  1. Time hidden
  2. Lifelines
  3. Over 90 days

Descriptive transcript

Time hidden runs from the commit that introduced a bug to the day it was caught, among bugs with a recorded introduction date. In this sample, 5 bugs hid for over 6 months.

Lifelines ordered by longest hidden put the longest-hidden bugs first. Sample bug #1400's line is among them: hidden for 107 days, fixed 17 days after it was caught.

The Hidden over 90 days view lists the 32 bugs that hid for over 90 days in the last 6 months. Sample bug #1400, hidden for 107 days, is one of them. Hidden time is reconstructed from recorded dates. Turnstone does not reveal bugs nobody has caught.

Turnstone is at turnstone.cloud.

5What Turnstone keeps

Turnstone keeps the facts.

What does Turnstone keep about #1400, and what stays in GitHub?

Facts, never content
More on Turnstone keeps the facts. Notes, chapters, and the transcript

Turnstone keeps the issue link, severity, area, cause, the two commits, and the dates. The title, the report, the failing test, and the evidence stay in GitHub.

It reads issues through a read-only connection and writes nothing back. If it lost all of its data, you would lose these charts and nothing else.

  1. What Turnstone keeps
  2. Read-only

Descriptive transcript

Turnstone keeps facts about bugs, never their content. For sample bug #1400 it kept the severity, area, cause, impact, change kind, and how it was caught. This is the real dashboard with sample data for Acme, a fictitious organisation.

For every bug, Turnstone keeps the issue link and number, state and severity, area, kind, cause, and impact, whether a campaign caught it, the commits that introduced and fixed it, and its dates. Issue titles and bodies, who wrote or fixed the code, regression tests, and evidence stay in your tracker.

Turnstone reads issues through a read-only connection and writes nothing back to GitHub or Gitea.

If Turnstone lost its data, you would lose the analytics and nothing else. Turnstone is at turnstone.cloud.

#1400 was one bug in Acme's sample.

Now look at yours.

Get startedThe CLI is free. Turnstone has a free tier.