Add postponed state to agile dashboard
Table of Contents
This page is a capture in the inbox bucket of the product backlog — a pre-sprint idea, not yet pulled into a sprint as a story.
What
Add a POSTPONED state to the agile dashboard story renderer. When a
story is returned to the product backlog at sprint close because it was
in-flight but could not finish (blocker, scope, or time), it currently
appears as BACKLOG — indistinguishable from stories that were never
touched. A POSTPONED state (or equivalent signal, e.g. a was_in_sprint
flag in the org frontmatter) would let the dashboard surface these items
distinctly: "started in sprint N, returned to backlog, carry forward."
Why
At sprint 20 close, BLOCKED and BACKLOG stories were returned to
product_backlog/next/ and their state normalised to BACKLOG to avoid
confusing the dashboard. The correct agile signal — "this story was
in-flight and needs to continue next sprint" — is lost. Without it,
sprint planning has no automated cue that these items have priority
over fresh backlog stories.
References
- Sprint 20 Postponed section in
doc/agile/versions/v0/sprint_20/sprint.org