pal-e-docs

Issue Template: Bug

template-issue-bug Template

active template
Project

Issue Template: Bug

Use this template for broken behavior, regressions, and unexpected failures. Bugs are Forgejo issues — not pal-e-docs notes. The legacy template-bug (pal-e-docs note template) is deprecated.

When to Use

  • Something that worked before is now broken (regression)
  • Behavior doesn't match documented acceptance criteria
  • Runtime errors, crashes, or data corruption
  • Alert firing that indicates a real problem (not noise)

Bug vs Feature vs Spike

Signal Type
It used to work, now it doesn't Bug
It never existed, we want it Feature
We don't know what's wrong or how to fix it Spike

Forgejo Issue Template

Lifecycle

Bugs follow the standard Forgejo issue lifecycle — no special tags needed. The issue is open while the bug exists and closed when the fix PR merges (via Closes #N in PR body).
  • template-issue-feature — feature variant
  • template-issue-spike — spike variant
  • template-issue — canonical issue design principle
  • convention-todo-lifecycle — lifecycle and triage rules