A bug is getting out of a monitor

Bug occurs when the actual result does not match the expected result.

Bug report is a document that records information about a found defect. A bug report is usually created by a tester, and the assignee is a developer responsible for the functionality.

Bug Report Format

Bug Report Attributes

ID: a unique identifier.

Title: a short summary that reflects the essence of the defect.

Status: the current stage of the fix.

Environment: the OS, browser version, or environment where the issue was found.

Priority: how urgent it is to fix the issue.

Severity: its impact on the system’s operability.

Steps: steps to reproduce the defect.

Expected result: what is supposed to happen.

Actual result: what actually happened.

* Comments, screenshots, videos.

Bug Report Example
ID: TT-7

Title: 500 Internal Server Error when logging in

Status: Created

Environment: Windows 11, Chrome 133.0

Priority: High

Severity: Blocker 🛑

Steps:

  1. Open the login page
  2. Enter login and password
  3. Click the «Log in» button

Expected result: The user successfully logs in.

Actual result: 500 Internal Server Error.

Screenshot.png


Bug report example in the JIRA issue tracker

Formula for a concise title

[ problem description ]

briefly describe what exactly is happening

[ place or component ]

where the error occurs (page, module, endpoint, etc.)

[ action or condition ]

under which actions or conditions the error occurs

For example:

[ Error message is not displayed ] [ on the login page ] [ when an incorrect password is entered ]

[ Total amount is not recalculated ] [ in the cart ] [ when a discount is applied ]

[ Content overflows the screen ] [ on mobile devices ] [ in portrait orientation ]

[ place or component ] can be omitted when the context is obvious.

[ action or condition ] can be omitted if the error does not depend on user actions.

How to determine bug severity?

Blocker

The bug makes the system unusable.

Example: it is impossible to pay for an order in an online store because of an error when creating the payment.

Critical

The bug causes data loss or breaks critical functionality.

Example: card payment with VISA does not work.

Major

The bug significantly affects how the system works.

Example: after placing an order, the user does not receive a confirmation email, but the order is saved in the system.

Minor

A small issue that does not interfere with core processes.

Example: a typo in the product description or a slightly misaligned product icon.
Task
Task available to premium users!
Sidebar arrow