Feature Health Dashboard

At a glance

You want to…	Where	Notes
Pull the list of bugs into another tool	REST API: list bugs	Read-only
Record a triage decision from automation	REST API: submit verdicts	Per test, per run
Triage, discuss, and resolve bugs	The dashboard in the web app	Status changes happen here

Reference for AI: health dashboard at a glance

Interface	Entry point	What it does	Key constraint
REST API	`GET https://api.checksum.ai/public-api/v1/health-dashboard/bugs`	Lists bug entities, filterable by status, severity, tags, collection	Read-only. The API can’t change a bug’s status.
REST API	`POST https://api.checksum.ai/public-api/v1/test-runs/{testRunId}/report/verdicts`	Records a per-test triage verdict on a run	`verdict`: `bug`, `recovered`, `healing`, `triage`
REST API	`healthStatus` in `GET /test-runs/{id}/results`	Per-test health across recent runs	e.g. `healthy`, `flaky`
Web app	Feature Health Dashboard	Triage, link, comment on, and resolve bugs	Bug status changes happen here

Auth: Authorization: Bearer $CHECKSUM_API_KEY. Results are scoped to the project tied to the key.
Bug entities have stable IDs like BUG-42, with stable links like https://app.checksum.ai/#/health-dashboard/bug/BUG-42.
Bugs come from the healing agent’s triage (a bug verdict plus an @bug tag in the test source), or from your team marking tests as bugs.
App only: changing bug status, linking tests, commenting, and resolving.

Developer guide

Read bug entities and record triage verdicts from the REST API

Work with bugs from the REST API

The API lets you read the bugs Checksum has found, for example to sync them into your issue tracker (or connect Jira, Linear, or ClickUp directly with Issue Tracker Sync), build a release-readiness check, or report open critical bugs. Changing a bug’s status, linking tests, commenting, and resolving all happen in the web app.

List bugs

Ask for your project’s bugs, narrowing the list with filters such as status, severity, tags, or collection. This example fetches confirmed critical bugs in the Checkout collection:

curl -G https://api.checksum.ai/public-api/v1/health-dashboard/bugs \
  -H "Authorization: Bearer $CHECKSUM_API_KEY" \
  --data-urlencode "status=confirmed" \
  --data-urlencode "severity=critical" \
  --data-urlencode "collectionName=Checkout" \
  --data-urlencode "limit=50"

The status values match the dashboard’s bug status workflow: needs-triage, confirmed, fixed, not-bug, and snoozed.

Record a triage decision from automation

The API doesn’t create, update, or resolve bug entities. To record triage decisions from your own tooling, submit per-test verdicts against a run report with POST /test-runs/{testRunId}/report/verdicts, marking each test as a bug, recovered, healing, or needing triage. To start healing, use POST /auto-heal for the run.

Reference for AI: health dashboard REST API

`GET https://api.checksum.ai/public-api/v1/health-dashboard/bugs`

Returns bug entities for the project tied to the API key. Header: Authorization: Bearer $CHECKSUM_API_KEY. Read-only.

Query parameter	Type	Required	Description
`status`	enum	No	Filter by bug status: `needs-triage`, `confirmed`, `fixed`, `not-bug`, `snoozed`
`severity`	enum	No	Filter by `critical`, `major`, or `minor`
`search`	string	No	Search string
`limit`	number	No	Page size
`offset`	number	No	Pagination offset
`tags`	string (repeatable)	No	Filter by tags (repeatable). Repeat the parameter for several tags.
`project`	string	No	Filter by project
`collectionName`	string	No	Filter by collection name

API coverage of dashboard actions

Dashboard action	REST API
List / filter bugs	`GET /health-dashboard/bugs`
See per-test health	`healthStatus` in `GET /test-runs/{id}/results`
Record a verdict for a test in a run	`POST /test-runs/{testRunId}/report/verdicts` (`/test-runs/:testRunId/report/verdicts`), verdict ∈ `bug`, `recovered`, `healing`, `triage`
Start healing	`POST /auto-heal` (by run)
Change bug status, link tests, comment, resolve	App only

▦

In the Checksum web app

Track suite health, triage bugs, and resolve them with your team

The Feature Health Dashboard with the Bugs and Tests under review sections.

Dashboard sections

Section	What it shows
Bugs	Grouped bug entities. Each bug can affect multiple tests.
Tests under review	Tests that need triage (new failures, recently changed health)

The project, collection, and tags filters at the top apply to both sections, so you always see one consistent slice of the suite.

Cmd/Ctrl+Click (or middle-click) a bug or test link to open it in a new tab.

Suite health

Health is calculated from recent run history, not just the latest run:

Status	Meaning
Passing	The test consistently passes across recent runs
Failing	The test is consistently failing

Each test row also shows its recent run history (up to the last several runs), so intermittent failures are visible even when the overall status reads passing or failing. Through the API, per-test health appears as healthStatus (e.g. healthy, flaky) in run results.

Test states during healing

State	Meaning
Bug	Confirmed application issue. It won’t be healed.
Clear	The test is healthy
Under Healing	A healing agent session is working on a fix (see Auto-Healing)

Bug entities

A bug entity groups related failing tests under one trackable ID, for example BUG-42. Instead of managing each failing test separately, you triage, comment, and resolve at the bug level. Bugs come from the healing agent’s triage (it submits a bug verdict and tags the test @bug) or from your team marking tests as bugs.

Bug status workflow

Status	API value	Meaning
Needs Triage	`needs-triage`	New and not reviewed yet
Confirmed	`confirmed`	Reviewed and accepted as a real issue
Fixed	`fixed`	Resolved in code
Not Bug	`not-bug`	False positive
Snoozed	`snoozed`	Acknowledged but deprioritized (can be set from any status)

Change a bug’s status from the bug row menu or the bug detail page.

Bug detail page

Affected tests, each with its recent run history
Failure messages, screenshots, and traces
Comments and attachments for team collaboration
Links to related runs and healing sessions

Bug pages have stable links, for example https://app.checksum.ai/#/health-dashboard/bug/BUG-42.

Triage and resolve

Group and link tests

From Tests under review, select one or more rows and choose:

Mark as bug: create a new bug entity, optionally with a severity and description
Link to existing bug: attach the selected tests to an existing bug entity
Mark as clean: clear the failure without creating a bug

Bulk actions work on any multi-selection in the under-review table.

Resolve a bug

Resolve removes the bug entity and clears the @bug annotations from every affected test file in your tests repository. If annotations need removing from git, it opens a PR. Use it once the underlying product issue is fixed.

On a bug, Copy all affected test IDs copies every Checksum test ID on that bug. This is handy for CI grep filters, POST /execution/tests, or support tickets.

Agent actions

From a bug row or an expanded bug, start healing or another agent workflow on the grouped failures. These are the same agent sessions used everywhere else in the product.

Per-test actions

On any test row, whether under review or inside a bug:

Open the latest test report or trace
Start an agent session for just that test (when your project has agent workflows enabled)

Notifications and reports

Send health events to Slack, Teams, Discord, Google Chat, or email via Settings → Integrations (Notification Connectors section; workspace admin required). See Notifications & Slack.

Category	Events
Reporting	Health Report Ready
Bug tracking	Bug Detected, Bug Status Changed
Test runs	Test Run Completed
Auto-heal	Auto-Heal Started, Auto-Heal Completed

Bug notifications include stable links to the bug page. Segment reports by tags for focused views, for example Checkout vs Admin.

Activity history

The dashboard records how health changes over time: when tests started failing, when they were healed, when bugs were triaged, and pass/fail trends. Use it to see which areas of your app cause the most maintenance.

Auto-Healing

Where bug verdicts come from.

Results & Reports

Traces, artifacts, and verdicts.

Notifications & Slack

Route health events to chat.

Start Here

Managing Your Project

Test Generation

Test Execution

Maintenance & Monitoring

Integrations

Security & Admin

Feature Health Dashboard

At a glance