Bugs
Bug Review is not enabled by default
Contact your project admin to enable this feature, or learn how to enable it yourself if you have admin access.
Bug Review helps you manage bugs detected by the AI Agent and avoid false positives. Reducing the noise and increase the accuracy and reliability of the AI Agent.
Overview
The Bugs view has two tabs: Bugs and Ignored Issues.
Bugs Tab
This tab displays all issues you’ve confirmed as real bugs. From here you can:
- Update bug information
- Add external links (Jira, Linear, GitHub, etc.)
- Toggle the “don’t re-report” flag
- Archive bugs when fixed
This tab is not filled automatically with every reported issue. You must manually confirm an issue as a bug during review for it to appear here.
Archiving Bugs
When a bug is fixed, archive it:
- Select one or more bugs in the Bugs tab
- Click the archive action
- Confirm the archive
What happens when you archive:
- The bug is marked as fixed and moved to archived status
- If “don’t re-report” was enabled, it’s cleared
- If this bug occurs again in the future, it will be reported as a new bug
- Archived bugs can be viewed by toggling the status filter to “all”
Archiving cannot be undone. Make sure the bug is actually fixed before archiving.
Ignored Issues Tab
This tab lists issues you’ve marked as not bugs (false positives). The AI Agent uses this list to avoid reporting similar issues in future runs.
By curating this list, you can reduce the noise and increase the accuracy and reliability of the AI Agent.
Ignored Issue Expiration
Ignored issues can expire after a configured number of days. When expired:
- The issue remains in your list but shows a warning indicator
- Expired issues are not included in the agent’s context
- The agent may start reporting similar issues again
Why expiration exists:
- Keeps the agent’s context fresh and relevant
- Prevents accumulation of outdated rules
- Agent gets smarter and certain rules are no longer needed
- Ensures ignored issues are periodically reviewed
To prevent expiration:
- Select the ignored issue(s) you want to keep active
- Click the “refresh” action
- This updates the modified date, resetting the expiration timer
The expiration time is configured at the project level. Contact your admin if you need to adjust it.
Review Workflow
When the AI Agent detects a potential bug during a test run, it creates a bug occurrence that needs your review.
Quick tip: The most impactful action is adding false positives to the Ignore List - this directly teaches the agent what not to report in future runs.
Starting a Review
- Go to History → Runs
- Select a run that includes reported bugs and open the Recording
- Navigate to a bug and click Review
The bug review dialog will open, showing the detected issue details and four action options.
Review Actions
When reviewing a bug occurrence, you have four options:
1. Create New Bug
Choose this when the report describes a genuine issue that should be fixed.
When to use:
- The agent found a real bug in your application
- This is a new issue not already tracked
What happens:
- A new bug record is created in the Bugs tab
- You can optionally enable “don’t re-report this bug” to prevent duplicate reports until it’s fixed
- You can add external links (Jira, Linear, etc.) after creation
Don’t Re-Report
Enabling “don’t re-report this bug” adds the bug to the agent’s context, preventing it from being reported again until archived or deleted. This reduces noise while the issue is being worked on.
Keep your bug list in sync. If a bug is fixed but not archived in Nexus, the agent won’t report it even if it regresses. Only use this feature if you regularly archive bugs when they’re fixed.
2. Add to Ignore List
Choose this when the agent incorrectly flagged something as a bug. Adding it to the ignore list teaches the agent to avoid this pattern in the future.
When to use:
- Intended behavior (works as designed)
- Expected error messages or validation
- Known limitations of the test environment
- The agent repeatedly makes the same mistake
What happens:
- The issue is saved to the Ignored Issues tab
- You must provide an explanation of why this is not a bug
- The agent uses this explanation as context in future runs to avoid similar false positives
The explanation you provide is important - it helps the agent understand what behavior is actually expected. Be clear and specific.
3. Link to Existing
Choose this when the detected issue is a duplicate of something already tracked. This is optional - if you don’t need to track duplicate occurrences, you can use Mark Reviewed instead.
When to use:
- The same bug has been reported before
- The issue matches an existing ignored issue
- You want to track how frequently an issue occurs
What happens:
- The occurrence is linked to the existing bug or ignored issue
- Helps track how often the same issue occurs
- Keeps your bug tracking organized
4. Mark Reviewed
Choose this when you’ve looked at the report but don’t need to create anything.
When to use:
- Build or configuration errors (not application bugs)
- Outdated test case issues
- One-off anomalies you don’t need to track
- You want to acknowledge the report without categorizing it
What happens:
- The occurrence is marked as reviewed
- No bug or ignored issue is created
- The review timestamp and reviewer are recorded
Review Status Tracking
For teams that need visibility into review progress, you can enable review status tracking in your project settings.
Test Plan History
If show_review_status is enabled, the test plan history and the test history shows a review status column indicating how many bugs have been reviewed. This is useful for ensuring all reported issues get triaged and for tracking overall review progress.
Status indicators:
- Reviewed (green): All bugs in the run have been reviewed
- Partial (yellow): Some bugs have been reviewed
- Pending (red): No bugs have been reviewed yet