Release 2.0.0 Task Board
Use this planning Board to inspect pending Tasks explicitly allocated to 2.0.0, together with the existing Tasks included by the Scope owner's planning decision. The two owner-requested UI corrections are included as unallocated backlog work. Membership and its per-Task source are maintained in the canonical Release record. The existing Release 1.0.0 Board remains unchanged.
- IN_BACKLOG
- READY_FOR_DELIVERY
- IN_PROGRESS
- TO_BE_RELEASED
View accessible data table
Read this Board
Cards and the accessible table distinguish three inclusion categories:
- Allocated to 2.0.0 — the canonical Task explicitly records this release.
- Carry-over planning inclusion · allocated to 1.0.0 — included for Release 2 planning by the owner; its canonical allocation remains 1.0.0.
- Unallocated planning inclusion — included by the owner without assigning a canonical release.
The decision names TASK-0164–0167, TASK-0171–0174, and TASK-0009/0010. Their current canonical status, parent Feature/Epic, owner, dependencies, and blockers are read from the canonical records, not copied into this page. Terminal and cancelled Tasks disappear automatically; no tasks are invented for Epics without tasks. Explicit allocations and planning inclusions are combined without duplicate cards.
Presence here changes neither allocation history nor implementation approval or Focus admission. Backlog work remains backlog until the required exact-item decisions are recorded. The Release 2.0.0 scope carries earlier Features forward, but cumulative Feature membership alone does not include every unfinished Task.
Open the accessible data table for linked Task, Feature, and Epic records, allocation labels, planning-decision evidence, and dependency status. Dependencies may belong to an earlier release: they remain linked prerequisites, not additional cards or invented release waves.