Issue Management

Boards

Each board groups issues along one label axis:

Board	Groups by	URL
Status	Status: label	https://gitlab.com/lasersenigma/lasersenigma/-/boards/1368218
Priority	Prio: label	https://gitlab.com/lasersenigma/lasersenigma/-/boards/7763186
Type	Type: label	https://gitlab.com/lasersenigma/lasersenigma/-/boards/7763189

The default day-to-day board is the Status board.

Rules

Every well-formed work item on the project MUST satisfy all of:

• Be an Issue work item (no Task, Epic, or other work-item type).
• Carry exactly one Type: label.
• Carry exactly one Status: label while open — a closed issue carries no Status: label.
• Carry exactly one Prio: label.
• Carry at least one Scope: label (multiple allowed).

Any of these missing or duplicated is a defect — the issue won't appear in its board column and downstream automation (dev-issue, version bump, changelog) will misroute it.

Status lifecycle

The Status: label follows the development lifecycle; the agent workflows apply these transitions systematically:

Event	Status label
Development starts (dev-issue)	Status: In Progress
Pushed / merged on main (dev-issue, final step)	Status: To release
Version tagged (release) → issue closed	Status label removed

A closed issue carries no Status: label. Manual pushes bypass the agent workflows — the triage skill catches the leftovers with a git-log cross-check on the (#NNN) commit references (best-effort: commits without an issue reference escape it).

Detection views

These saved views flag work items that violate the rules above:

View	What it lists	URL
Missing scope	No Scope: label	https://gitlab.com/lasersenigma/lasersenigma/-/work_items/views/1005860
Missing priority	No Prio: label	https://gitlab.com/lasersenigma/lasersenigma/-/work_items/views/1005861
Missing status	No Status: label	https://gitlab.com/lasersenigma/lasersenigma/-/work_items/views/1005862
Missing type	No Type: label	https://gitlab.com/lasersenigma/lasersenigma/-/work_items/views/1005863
Non-issue work item	Work item that is not an Issue	https://gitlab.com/lasersenigma/lasersenigma/-/work_items/views/1005866

Treat a non-empty view as a backlog of fixes — re-label or convert the offending items.

Allowed labels

Canonical list. Any label not below does not exist on GitLab — applying it will be rejected or (worse, for add_labels) silently create a new parasite label.

Live source: https://gitlab.com/lasersenigma/lasersenigma/-/labels (re-check there if a label might have been added or removed after this page was last touched).

Type (exactly one per issue)

• Type: Bug — For bug-related issues.
• Type: User Story — Functional changes, impacting users.
• Type: Technical story — No functional impact, only technical changes.
• Type: Non-dev task — No code impact at all: organisation, recruitment/HR, communication, level/game-design coordination, video, community.

Scope (one or more per issue)

• Scope: Lasers-Enigma plugin — Modify the lasers-enigma source code.
• Scope: LEPSU plugin — Modification of LEPSU plugin.
• Scope: SME plugin — Modification of Skytale Map Editor plugin.
• Scope: NESB plugin
• Scope: LE Play Server — In-game actions on LE Play server.
• Scope: Website
• Scope: Discord — Discord bots, administration, messages.
• Scope: Documentation — Actions on the GitLab wiki.
• Scope: DevOps — CI/CD, cloud server management, pterodactyl, bash, …
• Scope: Level Design — Levels to create/update/delete/order.
• Scope: Game Design — Game-designer skills, no dev help required.
• Scope: Skytale — Requested by or done by Skytale members.
• Scope: Video
• Scope: Team & Recruitment — Team building, management, HR, recruitment.

Status (exactly one per issue)

• Status: To do — Identified but not yet scheduled.
• Status: To Do Short term — Scheduled for upcoming work.
• Status: In Progress — Currently being worked on.
• Status: Code Review — Awaiting code review.
• Status: Paused/Blocked
• Status: Abandoned until ...
• Status: To release — Merged on main but not yet tagged.

Priority (exactly one per issue)

• Prio: HIGH
• Prio: MEDIUM
• Prio: LOW

Special / process flags (zero or more, independent of the rules above)

• Duplicate — Issue duplicates an existing one.
• Good for onboarding — Approachable, no complex refactor or 3-person handoff.
• Refactoring — Requires a code refactoring.
• Specifications required
• Technical Analysis required

For AI agents

Skills create-issue, edit-issue and triage MUST cross-check any label and the cardinality rules above against this page (or the live URLs) before composing the input file. Inventing a label is forbidden. Violating the cardinality rules is forbidden. If in doubt, ask the user. The triage skill treats non-compliance with the cardinality rules as the signal that an issue needs triage.