Intern
Tell me about the main attributes of a bug.
sobes.tech AI
Answer from AI
- ID: Unique identifier of the bug in the tracking system.
- Summary (Title/Description): A brief and clear description of the issue. It should be informative enough to give a general idea of the bug.
- Description (Full description): A detailed description of the problem, including steps to reproduce, actual result, and expected result.
- Steps to Reproduce: Clear and sequential instructions on how to reproduce the bug.
- Expected Result: How the system should have behaved in this situation.
- Actual Result: How the system actually behaved.
- Severity: The impact of the bug on system functionality. For example:
- Critical: Blocks the use of core functionality.
- Major: Disrupts main functionality but has workarounds.
- Minor: Does not disrupt main functionality but affects usability or appearance.
- Trivial: Minor errors, typos, not affecting functionality.
- Priority: How urgently the bug needs to be fixed. Determined by product management or the team. For example:
- High (Blocker/Urgent): Requires immediate fixing.
- Medium: Should be fixed in the next release.
- Low: Can be fixed in the future.
- Status: Current state of the bug in its lifecycle. For example:
- New: Just created.
- Open (Assigned): Assigned to a developer.
- In Progress: Developer is working on fixing.
- Fixed (Resolved): Bug fixed by the developer.
- Closed: Bug verified by QA and closed.
- Reopened: Bug reappeared after fixing.
- Rejected (Won't Fix): Bug deemed invalid or will not be fixed.
- Deferred (Postponed): Fix postponed to a later date.
- Environment: Information about the environment where the bug was found (operating system, browser, application version, hardware configuration).
- Attachments: Screenshots, logs, videos, or other files that help understand the bug and facilitate reproduction.
- Reporter: User who discovered and created the bug.
- Assignee: Developer responsible for fixing the bug.
- Created Date: Date and time when the bug was created.
- Last Updated Date: Date and time of the last change to the bug.
- Version: Version of the product or module where the bug was found and/or fixed.