Regression Bug Report Template

Regression Bug Report Template

Regressions are bugs introduced by recent changes that break previously working functionality. A dedicated regression template helps maintainers quickly identify the offending commit or release.

Why a Separate Template?

Standard bug reports focus on describing unexpected behavior. Regression reports need additional context:

• Last working version: Which version of the software worked correctly
• First broken version: When the regression was first noticed
• Changelog reference: Which release or commit likely introduced the issue

Template Structure

name: "Regression Report"
description: "Report something that used to work but is now broken"
title: "[Regression]: "
labels: ["bug", "regression", "priority:high"]
body:
  - type: input
    id: last_working_version
    attributes:
      label: "Last Working Version"
      description: "The most recent version where this feature worked correctly"
      placeholder: "v2.3.0"
    validations:
      required: true
  - type: input
    id: broken_version
    attributes:
      label: "First Broken Version"
      description: "The version where this stopped working"
      placeholder: "v2.4.0"
    validations:
      required: true
  - type: textarea
    id: expected_vs_actual
    attributes:
      label: "Expected vs. Actual Behavior"
      description: "What used to happen vs. what happens now"
    validations:
      required: true

Triage Benefits

By automatically applying the regression and priority:high labels, these issues get immediate attention. The version range information lets developers quickly run git bisect to find the exact commit that introduced the regression.

Best Practices

Include a dropdown for the affected component or module to route the issue to the right team. Add a checkbox asking whether the reporter has verified the behavior with the latest release.