Xeplosion commented

Owner

This is an Example Issue

This issue is currently in In Progress because substantive work has started and the issue is actively being executed.

At this stage:

Triage is complete and Resolution/Confirmed remains applied.
A valid Kind/ label is present.
The current Priority/ label should still reflect the issue's relative importance.
The issue has an active owner or contributor responsible for advancing the work.
Implementation, research, documentation, configuration, or other substantive execution is underway.
Start the Forgejo issue timer when beginning active work so time spent on the issue is recorded.
Stop the timer whenever active work pauses, the issue becomes blocked, or work shifts to another issue.
Resume the timer when substantive work on the issue continues.
Any newly discovered blockers, dependencies, or information requirements should be documented as they arise.
Active work should generally be limited to approximately 1–2 issues per person to avoid excessive work in progress.

The issue should remain in In Progress while active execution continues. Before moving it forward, ensure any active Forgejo timer has been stopped and the recorded time is accurate.

Once the substantive work is complete and the result is ready for validation, testing, approval, or merge, move it to In Review.

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 **In Progress** because substantive work has started and the issue is actively being executed. At this stage: * Triage is complete and `Resolution/Confirmed` remains applied. * A valid `Kind/` label is present. * The current `Priority/` label should still reflect the issue's relative importance. * The issue has an active owner or contributor responsible for advancing the work. * Implementation, research, documentation, configuration, or other substantive execution is underway. * Start the **Forgejo issue timer** when beginning active work so time spent on the issue is recorded. * Stop the timer whenever active work pauses, the issue becomes blocked, or work shifts to another issue. * Resume the timer when substantive work on the issue continues. * Any newly discovered blockers, dependencies, or information requirements should be documented as they arise. * Active work should generally be limited to approximately **1–2 issues per person** to avoid excessive work in progress. The issue should remain in **In Progress** while active execution continues. Before moving it forward, ensure any active Forgejo timer has been stopped and the recorded time is accurate. Once the substantive work is complete and the result is ready for validation, testing, approval, or merge, move it to **In Review**. ### 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 - [x] Assignee or active owner identified when appropriate - [x] Forgejo timer started when time tracking provides meaningful value - [x] Relevant implementation, research, or work notes recorded as needed - [x] 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

2026-09-04 18:54:54 +00:00

Xeplosion added this to the Project Template project

2026-09-04 18:54:55 +00:00

Xeplosion self-assigned this

2026-09-04 18:55:15 +00:00

Xeplosion added spent time

2026-09-04 18:56:36 +00:00

2 weeks 3 days

Xeplosion deleted spent time

2026-09-04 18:56:45 +00:00

- 2 weeks 3 days

Xeplosion added spent time

2026-09-04 18:57:04 +00:00

42 minutes

Xeplosion commented

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

Author

Owner

Aww man I was trying to add 420 days and 69 hours but the format was wrong... 😭

Xeplosion added reference docs

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

Xeplosion commented

2026-09-04 23:28:51 +00:00

Author

Owner

Left a comment explaining what work I have done so far, and started tracking my time working on this issue with the built-in Forgejo issue timer.

Left a comment explaining **what work I have done so far**, and **started tracking my time** working on this issue with the built-in Forgejo issue timer. ![image](/attachments/f551a888-0f5c-4257-b8be-29e222c27ee0)

image.png

4 KiB

Rows
Columns

Example 4 — In Progress #15

This is an Example Issue

Workflow Lifecycle

Triage

Backlog

To Do

In Progress

Review Gate

Completed