The issues board
Upliftr is AI debugging agents that work across your flow and your servers, read-only by design. When an agent confirms a failure in the browser, it root-causes it to the exact backend line and files it here, without ever mutating your code, data, or infrastructure. Upliftr ships a built-in tracker ("File to Upliftr") so you get a triaged board out of the box, and the same issues can be mirrored to GitHub, GitLab, or Jira.
What lands on the board
When the agent reproduces a failure and confirms it, Upliftr builds an issue carrying:
- a title and severity,
- a Markdown body, what failed, expected vs. observed, and (when a log backend is connected) the backend error, the suspected cause, and a suggested fix,
- the screenshot + step context from the run,
- a fingerprint for dedup.
The dashboard renders the body as Markdown; the issue detail also shows occurrences and an activity log.
Dedup by fingerprint
Each issue carries a stable upliftr-fingerprint derived from the suite, case, and failure signature. Re-filing the same failure doesn't create a duplicate, it bumps the issue's occurrence count and adds a comment. So a flaky check that fails every night is one issue that accrues history, not 30 tickets.
Triage in the dashboard
On the Issues page you can:
- filter by status (
open/acknowledged/closed) and search, - open an issue to read the full Markdown root-cause,
- edit the title, severity, and body,
- add comments, and
- move it through its lifecycle.
Over the API it's the /issues surface:
# List open issues
curl 'http://127.0.0.1:8400/api/v1/issues?status=open' -H "Authorization: Bearer $TOKEN"
# Acknowledge one
curl -X PATCH http://127.0.0.1:8400/api/v1/issues/UP-9 \
-H "Authorization: Bearer $TOKEN" -H 'content-type: application/json' \
-d '{"status":"acknowledged"}'Mirror to GitHub / GitLab / Jira
The built-in board is the default, but the same root-caused issue can be filed to your real tracker, deduped there too. Configure a provider and pick destinations with FILE_ISSUES (or per run). See Filing issues.
Related: Filing issues · Connecting server logs · REST API