279 — tp overview as a board: the phases left to right, issues filling each column (#279)
Why
tp overview (#274) is six lists down the page, ordered by what needs
the human. With real data, 28 roadmap items push the stories in
development and review off the screen, and the page does not show what
the flow is: a thought moving from idea to roadmap to story to landed.
A board with the phases across the top shows the movement at a glance
and where the work is piling up.
One group does not fit that reading. A called story is not a phase: its agent has stopped at whatever phase it was in and waits for an answer. On the page it reads as the first phase, and the word does not say what it means.
What changes
tp overview: the page is a board of five columns, left to right: Ideas, Roadmap, Not yet defined, In development, In review. Each heading has its count and links to that phase's documentation.- Each issue is a card in its column: the repository, the issue number linked to the forge, the title; a story in review links its pull request. Cards fill a column from the top, by repository, then issue number; there are no rows.
- A repository's cards carry a colour of its own, the same in every column, as a hint of which project a card belongs to.
- A called story is a card in the column of the phase it stopped in, flagged "blocked", the flag linking to what that means; within its repository it comes first. The "Called stories" list goes.
- More than five cards of one repository in one column: the first five are shown and the rest fold into a box, "… N more", that opens in place.
- The line "Needs you: N of LIMIT" stays above the board, counting as now: blocked stories and stories not yet defined.
docs/overview.md.
Acceptance
Which column an open issue of a level 3 repository is a card in.
"Pull request" is an open one from story/<N>-….
story |
defined |
Pull request | called |
Other flow label | Column | Flagged blocked |
|---|---|---|---|---|---|---|
| no | — | — | — | idea |
Ideas | no |
| no | — | — | — | roadmap |
Roadmap | no |
| yes | no | any | no | — | Not yet defined | no |
| yes | no | any | yes | — | Not yet defined | yes |
| yes | yes | none | no | — | In development | no |
| yes | yes | none | yes | — | In development | yes |
| yes | yes | open | no | — | In review, the pull request linked | no |
| yes | yes | open | yes | — | In review, the pull request linked | yes |
| no | — | — | — | none | no card | — |
One column, the cards of one repository in it:
| Cards | Blocked among them | Shown | In the box |
|---|---|---|---|
| 5 or fewer | any | all, by issue number, the blocked ones first | no box |
| 6 | none | the 5 lowest issue numbers | "… 1 more", holding the sixth |
| 12 | none | the 5 lowest | "… 7 more" |
| 8 | 2 | the 2 blocked, then the 3 lowest of the rest | "… 3 more" |
| 8 | 6 | the 5 lowest blocked | "… 3 more", the sixth blocked first in it |
The board:
| Condition | Outcome |
|---|---|
| cards in every column | five columns in the order above, each heading with its count (the cards in the box counted) and a link to its phase's documentation |
| a column with no cards | its heading with 0, and "none" |
| two repositories in one column | every card of the first, its box included, then the second's; by repository name |
| one repository in several columns | the same colour on each of its cards |
| two repositories | different colours |
| 2 blocked stories, 3 not yet defined and not blocked, limit 7 | Needs you: 5 of 7, as #275 counts |
| a forge not read | named above the board, as now |
Out of scope
- Renaming
calledin the label,tp story call, the docs and the manual (#281): until then only this page says "blocked". - Accepting a story from the page, and a link to the story's file (#280).
- Grouping by main project, and rows.
- Roadmap items in
ROADMAP.mdorder. - Choosing a repository's colour: it follows from its name.
Decisions
none
Done when
- tests express the acceptance table and pass
- spec updated
- ADR written if a fork was resolved
- changelog entry
- issue closed with a link to the release