28e38916f2
Switch from a custom CLI ticketing tool to Gitea-native issue tracking. Add issue templates (bug, feature, task) and a curated initial backlog of 20 tickets covering project foundation, testing, security, docs, features, and community maintenance.
Tickets
Central issue tracker and ticket backlog for the Arcline Project.
All work is tracked as Gitea Issues in this repository. No external tooling required — just open an issue.
Quick Start
Creating a Ticket
- Go to the Issues tab in this repo.
- Click New Issue.
- Pick a template:
- 🐛 Bug Report — something is broken.
- ✨ Feature Request — propose something new.
- 📋 Task / Epic — a general task, spike, or umbrella issue.
- Fill in the fields, attach labels, and submit.
The templates live in
.gitea/ISSUE_TEMPLATE/if you want to tweak them.
Labels
| Label | Purpose |
|---|---|
bug |
Defect or unexpected behaviour |
enhancement |
New capability or improvement |
task |
General work item |
epic |
Large body of work spanning multiple issues |
triage |
Needs prioritisation / hasn't been reviewed |
documentation |
Docs, READMEs, comments |
good first issue |
Beginner-friendly starting point |
blocked |
Waiting on something else |
wontfix |
Acknowledged but not planned |
Prioritisation
Prefix issue titles to signal urgency at a glance:
[P0]— Drop everything. Critical / blocking.[P1]— Important. Should be in the current iteration.[P2]— Nice to have. Backlog.[P3]— Someday / maybe.
Example: [P1] [Bug] Login page returns 500 on \n in username
Workflow
- Open an issue using a template.
- Triage — assign labels, priority, milestone, and an owner.
- Work — branch off
main, reference the issue in commits (#42). - Close — when the work lands, close the issue (or let a PR close it automatically with
Closes #42).
Backlog
See ISSUES.md for the initial curated backlog of tickets ready to be filed.