In that case, we can mark the bug as “Deferred” and plan to work on it in a future release of the software Deferred: Sometimes, we may decide that a bug doesn’t have a high priority – maybe it’s not a big problem, or it would be too difficult or expensive to fix right now.Duplicate: If the reported bug is the same as another bug already in the “Open” state or fixing a different bug will also take care of this one, it can be marked as a “Duplicate” so we don’t waste time working on it separately.Rejected: If a developer disagrees with a bug report from a tester and considers it’s not a problem or something that needs to be fixed right now, it can be marked as “Rejected”.Sometimes, after a bug has been reported and worked on, it goes through a few different states before it is resolved. If a previously closed defect is found to have a similar issue, it may be reopened and assigned for fixing again.
Let’s look into the visual representation of the various stages that a software defect goes through, from its discovery to closure:Īs we can see, the defect life cycle involves multiple stages, from triaging and assigning defects to developers for fixing to verifying the fix.
