Junior
How to classify bugs for the developer?
sobes.tech AI
Answer from AI
Bug classification helps developers quickly understand the problem and determine the priority of fixing. Main classification criteria:
- Severity: Impact of the bug on the application's operation.
- Blocker: The application is completely non-functional or key functionality is unavailable, with no workarounds.
- Critical: Serious functional violation affecting a significant number of users or key business processes. Partial workarounds or temporary solutions may be available.
- Major: Significant functional or usability issues, but without complete blockage.
- Minor: Insignificant functional issues, cosmetic defects, spelling errors. Does not significantly affect the application's operation.
- Trivial: Minor defects that hardly affect user operation, can be fixed last.
- Priority: Urgency of fixing the bug. Determined jointly by QA and Product Owner/Team Lead.
- Highest: Requires immediate fixing, blocks release or critically affects key users.
- High: Should be fixed soon, affects important usage scenarios.
- Medium: Preferably fixed before the next release.
- Low: Can be fixed in subsequent releases, not critical.
- Type: Category of defect.
- Functional: Error in functionality operation.
- UI/UX: Issues with appearance or usability.
- Performance: Performance issues (loading speed, responsiveness).
- Security: Security vulnerabilities.
- Compatibility: Errors related to operation on different devices, browsers, OS.
- Integration: Interaction problems between modules or systems.
- Usability: Difficulties in using the interface or performing tasks.
- Status: Current state of the bug in its lifecycle.
- New: Just created.
- Open: Accepted for work.
- In Progress: Being worked on.
- Fixed: Fixed by the developer.
- Pending Retest: Waiting for QA retesting.
- Reopen: Did not pass retesting, reassigned to developer.
- Closed: Successfully passed retesting.
- Rejected/Cannot Reproduce: Bug is not reproducible or not a defect.
- Deferred/Postponed: Fix postponed to a later date.
When providing information to the developer, clear steps to reproduce, actual and expected results, build/environment version, and logs are also important.