Example issues no longer match issue template structure

Xeplosion commented

2026-09-07 18:24:56 +00:00

Owner

Where is the problem?

The example issues in the Project Template project board are no longer up-to-date with the canonical issue templates in the main branch. The issue completion workflow has also changed and no longer matches the example issues.

Type of documentation issue

Outdated — the documentation no longer reflects the current system

What should change?

The issues and their comments should be updated to match the most recent versions of the issue template files, and the documentation files in the docs branch.

Source of truth / validation

Issue template files in the main branch
Documented workflow in the docs branch

Additional context

No response

Request checklist

I identified the documentation location or clearly described where the new documentation belongs
I described the intended corrected or improved content

Workflow lifecycle

Triage

Kind/ classification confirmed
Issue validity reviewed and appropriate Reviewed/ label assigned
Priority/ assigned when appropriate
Implementation branch referenced on the issue through Forgejo when applicable
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
Resolution is documented by a linked PR that closes the issue, or by a final issue comment explaining what changed, how it 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

### Where is the problem? The example issues in the [Project Template](https://git.xetech.online/XeplosionTechnologies/.forgejo/projects/4) project board are no longer up-to-date with the canonical issue templates in the `main` branch. The issue completion workflow has also changed and no longer matches the example issues. ### Type of documentation issue Outdated — the documentation no longer reflects the current system ### What should change? The issues and their comments should be updated to match the most recent versions of the issue template files, and the documentation files in the `docs` branch. ### Source of truth / validation - Issue template files in the `main` branch - Documented workflow in the `docs` branch ### Additional context _No response_ ### Request checklist - [x] I identified the documentation location or clearly described where the new documentation belongs - [x] I described the intended corrected or improved content ### Workflow lifecycle ### Triage - [x] `Kind/` classification confirmed - [x] Issue validity reviewed and appropriate `Reviewed/` label assigned - [x] `Priority/` assigned when appropriate - [x] Implementation branch referenced on the issue through Forgejo when applicable - [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 - [ ] Resolution is documented by a linked PR that closes the issue, or by a final issue comment explaining what changed, how it 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

labels

2026-09-07 18:24:56 +00:00

Xeplosion added this to the Forgejo Standards & Documentation project

2026-09-07 18:24:56 +00:00

Xeplosion added

and removed

labels

2026-09-07 18:25:34 +00:00

Xeplosion self-assigned this

2026-09-07 18:25:37 +00:00

Xeplosion added a new dependency

2026-09-07 18:25:46 +00:00

#28 Align pull request resolution with issue completion workflow

Xeplosion added a new dependency

2026-09-07 18:25:55 +00:00

#27 Standardize WIP pull request workflow

Xeplosion added the due date 2026-09-14

2026-09-07 18:26:04 +00:00

Xeplosion changed title from ~~Example issues not longer match issue template structure~~ to Example issues no longer match issue template structure

2026-09-08 10:10:46 +00:00

Xeplosion added a new dependency

2026-09-08 10:11:38 +00:00

#29 Build Xeplosion Technologies workflow and standards Wiki

Rows
Columns

Example issues no longer match issue template structure #33

Where is the problem?

Type of documentation issue

What should change?

Source of truth / validation

Additional context

Request checklist

Workflow lifecycle

Triage

Backlog

To Do

In Progress

Review Gate

Completed