This is an Example Issue

This issue is currently in Backlog because it has completed triage and has been confirmed as valid work, but it has not yet been selected for active execution.

At this stage:

A valid Kind/ label has been assigned.
Reviewed/Confirmed has been applied.
Any required clarification has been resolved.
Status/Needs Triage and Status/Needs More Info have been removed.
A Priority/ label should be present when priority can be determined.
Relevant Meta/ labels may remain applied.
The issue is accepted into the project scope, but it is not yet considered actively next in line.

The issue should remain in Backlog until it is deliberately selected and prioritized for upcoming work. Once it is ready to be worked next and has no known blockers preventing execution, move it to To Do.

Workflow Lifecycle

Triage

Kind/ classification confirmed
Issue validity reviewed and appropriate Reviewed/ label assigned
Priority/ assigned when appropriate
Applicable Branch/ label(s) assigned when branch targeting matters
Information requirements resolved; no Status/Needs More Info remains
Status/Needs Triage removed before leaving Triage

Backlog

Issue is confirmed valid and accepted into the project backlog

To Do

Scope and expected outcome are sufficiently defined
Known prerequisites, dependencies, and required decisions are resolved or understood
Work has been deliberately selected as upcoming work

In Progress

Assignee or active owner identified when appropriate
Forgejo timer started when time tracking provides meaningful value
Relevant implementation, research, or work notes recorded as needed
Forgejo timer stopped when active work ends, pauses, or becomes blocked

Review Gate

Review requirement assessed based on complexity, criticality, reversibility, and impact
If review is required: moved to In Review and appropriate testing / validation performed
If review is required: review comment records what was reviewed, how it was validated, findings, and outcome
If review is not required: rationale is evident from the low-risk nature of the change

Completed

Acceptance criteria / intended outcome satisfied
Related PRs, commits, documentation, or external changes linked where applicable
Final resolution comment explains what changed, how the issue was resolved, and how it was verified
Follow-up work split into separate issues where appropriate
Any Forgejo timer is stopped and recorded time is final
Issue moved to Completed and closed

# This is an Example Issue This issue is currently in **Backlog** because it has completed triage and has been confirmed as valid work, but it has not yet been selected for active execution. At this stage: * A valid `Kind/` label has been assigned. * `Reviewed/Confirmed` has been applied. * Any required clarification has been resolved. * `Status/Needs Triage` and `Status/Needs More Info` have been removed. * A `Priority/` label should be present when priority can be determined. * Relevant `Meta/` labels may remain applied. * The issue is accepted into the project scope, but it is not yet considered actively next in line. The issue should remain in **Backlog** until it is deliberately selected and prioritized for upcoming work. Once it is ready to be worked next and has no known blockers preventing execution, move it to **To Do**. ### Workflow Lifecycle ### Triage - [x] `Kind/` classification confirmed - [x] Issue validity reviewed and appropriate `Reviewed/` label assigned - [x] `Priority/` assigned when appropriate - [x] Applicable `Branch/` label(s) assigned when branch targeting matters - [x] Information requirements resolved; no `Status/Needs More Info` remains - [x] `Status/Needs Triage` removed before leaving Triage ### Backlog - [x] Issue is confirmed valid and accepted into the project backlog ### To Do - [ ] Scope and expected outcome are sufficiently defined - [ ] Known prerequisites, dependencies, and required decisions are resolved or understood - [ ] Work has been deliberately selected as upcoming work ### In Progress - [ ] Assignee or active owner identified when appropriate - [ ] Forgejo timer started when time tracking provides meaningful value - [ ] Relevant implementation, research, or work notes recorded as needed - [ ] Forgejo timer stopped when active work ends, pauses, or becomes blocked ### Review Gate - [ ] Review requirement assessed based on complexity, criticality, reversibility, and impact - [ ] If review is required: moved to **In Review** and appropriate testing / validation performed - [ ] If review is required: review comment records what was reviewed, how it was validated, findings, and outcome - [ ] If review is not required: rationale is evident from the low-risk nature of the change ### Completed - [ ] Acceptance criteria / intended outcome satisfied - [ ] Related PRs, commits, documentation, or external changes linked where applicable - [ ] Final resolution comment explains what changed, how the issue was resolved, and how it was verified - [ ] Follow-up work split into separate issues where appropriate - [ ] Any Forgejo timer is stopped and recorded time is final - [ ] Issue moved to **Completed** and closed

Xeplosion added the

Meta/Good First Issue

labels

Xeplosion added this to the Project Template project

Xeplosion added reference docs

2026-09-04 19:13:44 +00:00