Issues

An Issue contains a name, reproduction steps, expected and actual results, priority, source, and an optional linked Test Case. Occurrence history and related Runs help track repeated observations.

Sources

• Find issues: The QA Agent tests workflows directly and produces editable findings. Review, select, and click Create to save new Issues without linked Test Cases. See Find issues.
• Runs: A failed background case execution can create or link an Issue when it includes an issue report. A failure without a report does not necessarily create an Issue.
• Manual: Enter a report yourself, optionally linking a project Test Case.

Manual reports can match an existing open Issue in the project by title. Run findings match only open Issues for the same Test Case. A match adds an occurrence and keeps the original report and priority. Find issues uses existing reports as discovery context, but saving its selected drafts creates new Issues rather than merging them at save time.

Review evidence

Read reproduction steps and expected versus actual behavior before deciding how to act. A direct finding may have a Reproduction video. For Run findings, inspect Related Runs and their recordings when available. Recordings may still be processing when the Issue first appears.

Resolve and reopen

The main workflow is Open → Resolved, with a required resolution reason. Explain whether the product, case instructions, data, or environment changed. Resolution does not automatically rerun tests or prove a fix.

Reopen returns a resolved or ignored Issue to Open and clears its resolution reason and time. Historical triaged Issues can also be resolved. New Run findings match only open Issues; a recurrence after resolution can create a new report instead of reopening the old one.