docs(issue-tracking): add the blocked triage state and the epic-closing rule #59

Sammanfogat

supernaut sammanfogade 1 incheckning från docs/issue-tracking-blocked-label in i main

2026-07-31 00:59:28 +00:00

supernaut kommenterad

2026-07-30 22:42:56 +00:00

Ägare

Three conventions that were missing, each found by a board drifting away from the truth rather than
by reading the guide.

`blocked`

bitborg-infra#39 (migrate off-site backups to Bahnhof S3) has been fully evaluated for weeks. It
cannot be picked up because Bahnhof has not released the product. The only label that fit was
needs-triage, whose stated meaning is "not yet evaluated" — the opposite of the truth, and enough
to make the issue look neglected in every triage sweep.

Adds a blocked triage state (created org-wide, applied to #39) and a lifecycle step saying to
record what it waits on and to drop the label when the dependency clears.

When an epic closes

Roadmap epics bitborg-docs#51 (sign-up trial) and #54 (ADR 0037 reconcile trigger) both sat in the
Shipped column while still open. In each case the build scope was fully delivered and what
remained was not building: an operator-gated end-of-August downgrade in one, a phase explicitly
deferred to the payments programme in the other.

There was no written rule, so both stayed open — which meant the Shipped column described delivered,
production-verified work as pending. That is the more misleading of the two available errors. The
rule now: build scope delivered closes the epic; a dated operational remainder becomes its own task
in the repository that will carry it out, linked from the closing comment.

Boardless task issues

bitborg-docs#14 (write ADR 0026) has been open since 10 July and appeared on no board, because
bitborg-docs had no project board — the guide only named bitborg-infra and bitborg-web as
task-bearing repositories. A Bitborg Docs board now exists and #14 sits on it.

States plainly that every repository holding task issues has a board, and that a task in a boardless
repository is invisible work.

markdownlint and Prettier clean.

Three conventions that were missing, each found by a board drifting away from the truth rather than by reading the guide. ## `blocked` bitborg-infra#39 (migrate off-site backups to Bahnhof S3) has been fully evaluated for weeks. It cannot be picked up because Bahnhof has not released the product. The only label that fit was `needs-triage`, whose stated meaning is "not yet evaluated" — the opposite of the truth, and enough to make the issue look neglected in every triage sweep. Adds a `blocked` triage state (created org-wide, applied to #39) and a lifecycle step saying to record _what_ it waits on and to drop the label when the dependency clears. ## When an epic closes Roadmap epics bitborg-docs#51 (sign-up trial) and #54 (ADR 0037 reconcile trigger) both sat in the **Shipped** column while still open. In each case the build scope was fully delivered and what remained was not building: an operator-gated end-of-August downgrade in one, a phase explicitly deferred to the payments programme in the other. There was no written rule, so both stayed open — which meant the Shipped column described delivered, production-verified work as pending. That is the more misleading of the two available errors. The rule now: build scope delivered closes the epic; a dated operational remainder becomes its own task in the repository that will carry it out, linked from the closing comment. ## Boardless task issues bitborg-docs#14 (write ADR 0026) has been open since 10 July and appeared on no board, because bitborg-docs had no project board — the guide only named bitborg-infra and bitborg-web as task-bearing repositories. A **Bitborg Docs** board now exists and #14 sits on it. States plainly that every repository holding task issues has a board, and that a task in a boardless repository is invisible work. --- `markdownlint` and Prettier clean.

supernaut lade till 1 incheckning

2026-07-30 22:42:56 +00:00

docs(issue-tracking): add the blocked triage state and the epic-closing rule

ci / ci (pull_request) Successful in 12s

Detaljer

b34f691185

Three gaps surfaced during a board audit.

**No state for "evaluated but externally blocked."** gitborg-infra#39 (migrate off-site S3 to
Bahnhof) is fully understood and simply waiting on a vendor to ship a product, but the only label
that fit was `needs-triage` — which asserts the opposite of the truth, that nobody has looked at it.
Adds `blocked` and says when to reach for it.

**No rule for when an epic closes.** Two Roadmap epics sat in the Shipped column while still open,
because each had a non-build remainder: an operator-gated downgrade in one case, a phase deferred to
a later programme in the other. Waiting on those left Shipped describing delivered work as pending.
The rule: build scope delivered closes the epic, and the remainder becomes its own task.

**Boardless task issues.** gitborg-docs held an open task but had no project board, so the work
appeared on nothing. Records that gitborg-docs carries decision-record and documentation tasks, and
that a task in a boardless repository is invisible work.

supernaut sammanfogade incheckning c2d19a4562 till main

2026-07-31 00:59:28 +00:00

supernaut tog bort grenen docs/issue-tracking-blocked-label

2026-07-31 00:59:28 +00:00

supernaut refererade denna ändringsförfrågan från en incheckning

2026-07-31 00:59:30 +00:00

docs(issue-tracking): add the blocked triage state and the epic-closing rule (#59)

supernaut refererade denna ändringsförfrågan från en incheckning

2026-08-03 09:41:31 +00:00

docs(issue-tracking): add the blocked triage state and the epic-closing rule (#59)

Logga in för att delta i denna konversation.

Inga granskare