pal-e-docs

Issue Template: Feature

template-issue-feature Template

active template
Project

Issue Template: Feature

Use this template for new functionality, enhancements, and user stories. This is the default issue type — if no ### Type header is present, validation falls back to this template.

When to Use

  • New feature or capability
  • Enhancement to existing functionality
  • Planned work scoped from a plan phase
  • Any work that isn't a bug fix or exploratory spike

Forgejo Issue Template

Feature Flag Section

Added 2026-06-07. Forces ticket authors to decide whether a feature flag is needed before work starts. The agent reads the repo's docs/feature-flags.md for the flag design — naming conventions, resolution order, how to register and gate. If the repo has no feature flag doc, the section is skipped with "none".
This pairs with the PR body template's feature flag checklist item, which verifies the flag was actually implemented as specified.

Relationship to template-issue

This template contains the same sections as the original template-issue, with the addition of the ### Type header and ### Feature Flag section. The original template-issue remains as the canonical reference for the issue-as-spec design principle. This template is what check-issue-template.sh validates against when ### Type is Feature or absent.
  • template-issue — canonical issue design principle and history
  • template-issue-bug — bug variant
  • template-issue-spike — spike variant
  • template-pr-body — PR-side feature flag checklist
  • convention-todo-lifecycle — lifecycle and triage rules