Bug Tracker
Automatic bug entry creation from test failures — with full context, screenshots, and reproduce steps — so nothing gets lost between test runs and your issue tracker.
What this module does
The Bug Tracker module is not a standalone test type — it is an integration layer that receives signals from the other modules and the ResultAnalyzer agent. When a failure is classified as a Product Bug, the Bug Tracker module automatically creates a structured bug entry containing everything a developer needs to reproduce and fix the issue.
Bug entry contents
Each automatically created bug entry includes:
- Title — derived from the failed test scenario title
- Severity — inferred from the module (Security critical findings are High; functional failures are Medium by default)
- Steps to reproduce — the test's KB scenario steps
- Expected behaviour — from the KB scenario
expectedfield - Actual behaviour — the assertion failure message and actual observed value
- Screenshot — for Web UI failures, the screenshot at point of failure
- Run reference — link to the specific run and test result
- Environment — the environment the test ran against
- First seen / Last seen — if the bug was detected in previous runs
Bug lifecycle
| Status | Description |
|---|---|
| Open | Bug first detected. Assigned to the team or left unassigned. |
| In Progress | A team member has started working on the fix. |
| Fixed | Marked as fixed by a team member. VigilQA monitors subsequent runs for re-occurrence. |
| Verified | The test that detected the bug now passes. Automatically updated by VigilQA after the fix is verified. |
| Reopened | A fixed bug failed again in a subsequent run. Automatically transitioned. |
| Wont Fix | Manually dismissed — the bug is known and accepted. |
Deduplication
VigilQA deduplicates bug entries. If the same test scenario fails in consecutive runs, the existing Open bug is updated (last-seen timestamp, run count) rather than creating a duplicate entry. A new entry is only created if the previous bug was marked as Fixed or Wont Fix.
External issue tracker integration
Bug entries can be mirrored to external issue trackers. Currently supported:
- Jira — creates Jira issues in a configured project; syncs status bidirectionally
- Linear — creates Linear issues; syncs resolution status
- GitHub Issues — creates GitHub issues with full context
Configure integrations in Settings → Integrations → Bug Tracker.
External integration is one-directional by default: VigilQA creates issues in the external tracker, and when the test passes in a subsequent run, VigilQA adds a comment noting the fix verification. Full bidirectional sync (closing VigilQA bugs when Jira issues close) can be enabled per integration.