Defect Management for Quality Assurance (QA)s
Defect management is how a team records, prioritises, tracks and closes bugs. A good bug report gives a clear title, exact reproduction steps, expected and actual results, environment and evidence. Tools such as Jira hold the workflow from new through fixed and verified to closed.
Stage: Testing Fundamentals · Part of the Quality Assurance (QA) roadmap · Last reviewed 19 November 2026
What to learn in Defect Management
- Write a bug title that states the failure and where it happens
- List reproduction steps that another person can follow exactly
- Attach logs, screenshots or a short screen recording as evidence
- Assign severity and priority and explain how they differ
- Follow a bug through a Jira workflow and its statuses
- Decide when a report is a duplicate, invalid or not reproducible
Defect Management interview questions
What is the difference between severity and priority?
Severity measures the technical impact of a defect on the system, such as a crash or data loss. Priority is how soon the business wants it fixed. A typo on the home page is low severity but can be high priority.
What do you do when a developer cannot reproduce your bug?
Re-check the steps, environment, build version and test data, then add logs, a recording and exact inputs. Try it on a clean setup and sit with the developer if needed. Intermittent bugs should note the frequency and any timing pattern.
Where Defect Management fits in the Quality Assurance (QA) roadmap
Defect Management belongs to the Testing Fundamentals stage (beginner level), which takes about 7 hours. Think like a tester.
Other units in this stage
Back to the full Quality Assurance (QA) roadmap