Normalize Bug Report

Goal

• Bug report structured as sections, with no initial information lost.

Input

• Raw bug report: freeform description, error log, or structured text. May be a single report, or an itemized batch (each with its own

  id

  ) - keep

  id

  attached throughout.

Steps

Step 1: Structure Bug Report

• Title: Issue statement. Focus on the issue, not the fix - declare the current, incorrect behavior (e.g. "User cannot log in")
• Pre-conditions: Prerequisites for reproducing the bug (e.g. system state, environment, user account, or configuration).
• Steps to Reproduce (STR): Sequential actions triggering the bug.
• Actual Result (AR): Incorrect behavior description (e.g. error message).
• Expected Result (ER): Correct expected behavior (e.g. notification shown).
• Evidence: Assets with symptoms (e.g. logs, screenshots).
• Severity: Level of impact (e.g., critical, high, medium, low).

Output

• Bug Report
  • Title
  • Pre-conditions
  • Steps to Reproduce (STR)
  • Actual Result (AR)
  • Expected Result (ER)
  • Evidence
  • Severity