Defects track bugs discovered during test execution and connect them to the cases and runs where they surfaced.
When a test case fails, the natural next step is to record what went wrong. Defects in Qase formalize that,each defect captures the actual result, severity, and (optionally) a link to your external issue tracker. Defects created during a run automatically link back to the specific case and result that triggered them, giving you full traceability from failure to fix.
If you use an issue tracker integration (Jira, GitHub, GitLab, Linear, etc.), you can create or link external issues directly from the defect, without leaving Qase.
Creating defects
From a test run (recommended)
This is the most common path. When you mark a case as Failed or any other negative result during a run:
1. The result dialog appears. Check Create/attach defect (this checkbox is checked by default if you've enabled it in project settings).
2. Choose whether to create a new defect or attach an existing one, useful when multiple cases fail due to the same underlying bug.
3. Fill in the defect properties: title, actual result, severity, and any custom fields configured for defects.
4. Optionally, create or link an issue in your connected issue tracker.
The defect is now visible in the run's Defects tab and in the project wide Defects section.
If Fail case on step fail is enabled in project settings, failing any single step auto-fails the entire case and prompts defect creation immediately.
From the defects section (standalone)
You can also create defects outside of a run, useful for documenting known issues before testing begins or for bugs found outside formal test execution.
Go to the Defects section and select Create New Defect. Provide the title, actual result, severity, custom fields, and optional attachments.
Standalone defects won't have a linked test case or run, but they can still be attached to future run failures. This is helpful when you know about an issue beforehand and want run-time defects to reference it rather than creating duplicates.
Defect lifecycle
Every defect follows a simple status workflow:
Status | Meaning |
Open | Newly created. The bug exists and hasn’t been addressed yet. |
In Progress | Someone is actively working on a fix. |
Resolved | The fix is complete. Marked with a green icon in the defects list. |
Invalid | The reported issue isn’t actually a bug (misunderstanding, expected behavior, etc.). |
Transitions are straightforward: Open → In Progress → Resolved. You can invalidate a defect from any state.
Linking to external issue trackers
If you have an issue tracker integration installed, you can:
Create a new issue in the external system directly from Qase — the defect details populate the issue automatically.
Link an existing issue by searching for it within the defect dialog.
This works both when creating a defect during a run and when editing a defect after the fact. The link is bidirectional: the Qase defect shows the external issue ID, and (depending on the integration) the external issue links back to Qase.
Managing defects
The Defects section shows all defects in a project. You can:
Search by title or description.
Filter by status, severity, assignee, linked external issue, or any custom field.
Edit a defect to update its title, actual result, severity, attachments, or custom fields.
Clicking a defect opens its detail view, showing the linked test run, test case, reporter, creation date, and full history.
Defect scope: The defects tab within a specific run shows only defects filed in that run. The project-level Defects section shows all defects across all runs.
FAQ
What happens to a defect if I delete the test run it came from?
The defect itself stays in the project-level Defects section; it just loses its linked run reference. Your bug record isn't deleted with the run.
If I resolve a defect in Jira, does it auto resolve in Qase?
Most integrations sync status changes bidirectionally, but check your specific integration settings.
If your integration supports status sync, make sure you've mapped the statuses in the Qase app settings.
Can I attach the same defect to multiple test cases?
Yes. When recording a failure, choose Attach existing defect and select the defect. This is the right approach when multiple cases fail due to the same root cause.