#Defects FAQs - Bug Tracking Questions

#What is a defect?

A defect is an issue or bug found in software during testing or reported by users. It represents a problem that needs to be identified, tracked, and resolved.

#How do I create a defect?

To create a defect:

1. Navigate to the Defects page
2. Click “Create Defect”
3. Fill in defect details (title, description, priority, severity)
4. Optionally link to test cases or requirements
5. Add attachments if needed
6. Click “Create”

See the Creating Defects guide for details.

#Can I create a defect from a failed test case?

Yes, you can create a defect directly from a failed test case. This automatically links the defect to the test case and includes relevant context.

#What’s the difference between priority and severity?

• Priority: How urgent it is to fix the defect (business impact)
• Severity: How severe the impact is if the defect occurs (technical impact)

A defect can have high severity but low priority, or vice versa.

#How do I track defect status?

Defects progress through various statuses:

• New: Just reported
• In Progress: Being worked on
• Resolved: Fixed, awaiting verification
• Verified: Confirmed fixed
• Closed: No further action needed

See the Tracking Defects guide for the complete lifecycle.

#Can I link defects to test cases?

Yes, you can link defects to test cases. This helps track which test cases discovered defects and ensures test cases are updated when defects are fixed.

#How do I know if a defect is fixed?

When a developer marks a defect as “Resolved”, it moves to verification. You can then re-execute the related test case to verify the fix. Once verified, mark the defect as “Verified” or “Closed”.