# This is an Example Issue This issue is currently in **Triage** because it is still being classified and evaluated before entering the working backlog. During triage: * Exactly one `Kind/` label must be assigned to identify the type of work. * A `Priority/` label should be assigned when urgency can be reasonably determined. * A `Resolution/` label is required before the issue can leave Triage. * Valid issues receive `Resolution/Confirmed`. * Invalid, duplicate, or declined issues receive the corresponding resolution and are closed. * `Status/Needs Triage` remains applied while evaluation is in progress. * If additional information is required, replace it with `Status/Needs More Info` and keep the issue in **Triage**. * Relevant `Meta/` labels may be applied as additional contributor or workflow signals. * `Compat/` labels are generally reserved for pull requests and are not part of normal issue triage. Once the issue has a valid `Kind/`, an appropriate `Resolution/`, no unresolved information requirements, and triage is complete, the `Status/` label can be removed and the issue moved to **Backlog**. ### 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

Xeplosion commented

2026-09-04 18:39:06 +00:00

Owner

This is an Example Issue

This issue is currently in Triage because it is still being classified and evaluated before entering the working backlog.

During triage:

Exactly one Kind/ label must be assigned to identify the type of work.
A Priority/ label should be assigned when urgency can be reasonably determined.
A Resolution/ label is required before the issue can leave Triage.
- Valid issues receive Resolution/Confirmed.
- Invalid, duplicate, or declined issues receive the corresponding resolution and are closed.
Status/Needs Triage remains applied while evaluation is in progress.
If additional information is required, replace it with Status/Needs More Info and keep the issue in Triage.
Relevant Meta/ labels may be applied as additional contributor or workflow signals.
Compat/ labels are generally reserved for pull requests and are not part of normal issue triage.

Once the issue has a valid Kind/, an appropriate Resolution/, no unresolved information requirements, and triage is complete, the Status/ label can be removed and the issue moved to Backlog.

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