Vertical: impact on clubs/members (top = high). Horizontal: effort for the dev team (left = small). "This sprint" tags = Rhys's current picks. 👍 = GitLab votes.
Quick wins
High impact · low effort — best return on scarce dev time
Big bets
High impact · high effort — need planning, one at a time
Fill-ins
Low impact · low effort — ideal first contributions for new volunteers
Question marks
Low impact · high effort — park unless someone champions them
Probably done — verify & close
Implemented / awaiting verification (e.g. "Testing v2.3x" labels) — a quick check could close these
Possibly stale — confirm & archive
Superseded, handled offline, or too old/vague to action — nominated for closure, team decides
Blocked / waiting
Can't reproduce or waiting on information
This already exists in GitLab — how it would work for real
This page is only the sandbox for agreeing a starting arrangement. GitLab CE has the movable version built in:
- Create seven scoped labels on the project:
triage::quick-win,triage::big-bet,triage::fill-in,triage::question-mark,triage::verify-close,triage::stale,triage::blocked(scoped = an item can only hold one at a time). - Apply the agreed starting arrangement to all 93 items in one scripted pass via the API (script ready — takes a minute to run).
- Create an Issue Board (Plan → Issue boards) with one column per label. From then on, dragging a card between columns on the board is the reclassification — shared, live, permissioned, no extra tools.
Until then: rearrange here, hit "Export JSON", and post it in the group — your version can be merged into the proposal before anything touches GitLab.