Issues

Issues flag the cause of a test failure, a UI/UX improvement, or an unclear test instruction, and cite exactly where in the run or instructions it occurred. Individual issues are grouped in the background into Issue Groups, shown on the Issues and Overview pages.

​

Individual Issues

Issues are generated per flow run. View them on a flow run directly, or through the occurrences in an issue group. A flow run shows what happened; an issue group shows where similar issues happened across your runs. Each issue has the following properties:

​

Issue Groups

An Issue Group collects individual issues that describe the same underlying problem, even when they occur on different runs, flows, apps, or devices. Grouping is semantic, so issues match on meaning rather than exact wording, and runs in the background: new issues join existing groups automatically, duplicate groups merge, and overly broad groups split. Each group falls into one of three categories:

• Critical: App bugs responsible for test failures. Any group that contains a critical issue.
• UI/UX: Visual, usability, and performance improvements that didn’t fail the test.
• Instruction: Instructions the agent found ambiguous, contradictory, or impossible on the current build. These point to the test, not your app.

A group shows:

• Occurrences: The total times the problem has been seen.
• Affected flows, apps, devices, and builds: The places where it occurs.
• Severity breakdown: The count of critical, major, and minor issues in the group.
• First and last seen: The times when the problem started and when it last occurred.
• Evidence: The runs where it occurred, each with a screenshot from the exact action.

​

Triage

Every group has a status. Use the status toggle on the Issues page to filter by New, Dismissed, Closed, or All. Statuses are shared across your workspace.

​

Create a Jira or Linear ticket

When Jira or Linear is connected, select Create ticket from an issue group or from an individual issue on a flow run. Review the provider, destination, issue type, title, and description before creating the ticket. Autosana prefills the editor from the existing issue analysis and evidence; you can edit the title and description without changing the Autosana issue. Autosana shows the external ticket key after creation and prevents a second current ticket for the same issue group. A pending result shows that creation is still in progress. If the result is unknown, check Jira or Linear before retrying. Completed and failed attempts remain in the issue group’s ticket history. Workspace admins can optionally choose Jira or Linear as the single automatic provider under Settings > Integrations. Automatic creation applies to new critical issue groups and still creates at most one current ticket. Ticket behavior follows issue triage:

​

Next Steps

• Learn how flows are reviewed
• Get notified when runs complete
• Track performance metrics on every run