This is an Example Issue

This issue is currently in To Do because it has been selected from the backlog, prioritized, and is ready for execution.

At this stage:

Triage is complete and Resolution/Confirmed remains applied.
A valid Kind/ label is present.
A Priority/ label should reflect its current execution priority.
The scope and expected outcome are sufficiently defined.
Any required dependencies, prerequisite decisions, or information needs have been resolved.
The issue has been deliberately selected as upcoming work rather than remaining in the general backlog.
No active implementation work has started yet.

The issue should remain in To Do until someone begins substantive work on it. Once execution starts, move it to In Progress.

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 **To Do** because it has been selected from the backlog, prioritized, and is ready for execution. At this stage: * Triage is complete and `Resolution/Confirmed` remains applied. * A valid `Kind/` label is present. * A `Priority/` label should reflect its current execution priority. * The scope and expected outcome are sufficiently defined. * Any required dependencies, prerequisite decisions, or information needs have been resolved. * The issue has been deliberately selected as upcoming work rather than remaining in the general backlog. * No active implementation work has started yet. The issue should remain in **To Do** until someone begins substantive work on it. Once execution starts, move it to **In Progress**. ### 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 - [x] Scope and expected outcome are sufficiently defined - [x] Known prerequisites, dependencies, and required decisions are resolved or understood - [x] 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:32 +00:00