How issues are created
When a run finishes, TesterArmy records its findings as project issues:
Non-blocking warnings, such as accessibility audit findings, stay on the run report and are not added to the Issues tab.
Deduplication and occurrences
Repeat sightings of the same bug fold into one issue instead of creating new rows. TesterArmy matches reports on the bug name and page, and also folds reports that describe the same bug in different words on the same page. Step failures match on the step and the test, so the same step title failing in two different tests stays two issues. Every fold adds an occurrence. The issue page lists them under Occurrences, with each run’s status, environment, trigger, duration, and start time, and shows the most recent evidence under Latest occurrence.Environments
Issues are bound to the environment of the run that found them. The same bug on Production and on Staging is tracked as two separate issues. By default the list shows Live environments, which excludes PR previews: preview failures are reviewed in the pull request flow. Open preview issues that are not seen again for 7 days are resolved automatically. Switch to All environments or a single environment to see them.Statuses
Change a status from a row’s actions menu (Mark as resolved, Mark as false positive, Reopen), or from the issue page with Mark resolved and its overflow menu. Use Mark as duplicate on an open row to resolve it as a duplicate. Delete on the issue page removes the issue entirely.
To triage many issues at once, select rows with their checkboxes and use the bar at the bottom of the screen. Up to 100 issues can be selected at a time.
Filter and sort
Filters are kept in the page URL, so you can reload or share a filtered view.
Export to Linear or Jira
Open an issue and click Create ticket to export it to a connected tracker. When both Linear and Jira are connected, or neither is, Create ticket opens a menu to pick the tracker. Rows also offer Create Linear ticket and Create Jira ticket in their actions menu. After export, the issue links to its ticket (for exampleENG-42) instead of offering a new export.
Fix with a coding agent
On the issue page, Copy prompt to fix copies a debugging prompt built from the issue’s evidence. Use the menu next to it to open the prompt directly in Cursor, Claude Code, or Codex.Read issues from the API and MCP
Issues are available read-only to automation. Triage and ticket export stay in the dashboard.
Both list surfaces accept
status (open, resolved, false_positive), environment (production, staging, preview, custom), and limit (1-100, default 50). The detail includes reproduction steps, expected vs actual behavior, severity, occurrence count, the linked ticket, and recent run occurrences. See the API Reference and MCP server.