docs(memory): record what puts a WSP ticket on the Flamingo board #114

2026-09-01T10:29:26+01:00

lyrathorpe commented

2026-09-01 10:29:26 +01:00

Board 411 was silently dropping newly-created tickets, and none of the fields we assumed were responsible.

The board filters on membership of the saved filter Flamingo - CommittedWork (or the stf-flamingo-help label), and applies a sub-filter of fixVersion in unreleasedVersions() OR fixVersion is EMPTY. Four tickets were invisible because they carried MultiCluster v18.0.12, released 2026-08-25 — including one still In Progress.

Flamingo - CommittedWork turns out to be curated rather than computed: of its 100 most recently updated members, 52 have no Team and 94 no PI Commitment, and its components span the whole product. So Team, PI and PI Commitment are worth setting for PI planning but will never move the board.

The memory records the filter verbatim, the two conditions a new ticket must meet, the 30-day Done window, and the field IDs and current values (PI 26Q4, Committed), plus the note that field names cannot be resolved through the MCP tools.

Needs a rebuild to take effect.

Board 411 was silently dropping newly-created tickets, and none of the fields we assumed were responsible. The board filters on membership of the saved filter `Flamingo - CommittedWork` (or the `stf-flamingo-help` label), and applies a sub-filter of `fixVersion in unreleasedVersions() OR fixVersion is EMPTY`. Four tickets were invisible because they carried `MultiCluster v18.0.12`, released 2026-08-25 — including one still In Progress. `Flamingo - CommittedWork` turns out to be curated rather than computed: of its 100 most recently updated members, 52 have no Team and 94 no PI Commitment, and its components span the whole product. So Team, PI and PI Commitment are worth setting for PI planning but will never move the board. The memory records the filter verbatim, the two conditions a new ticket must meet, the 30-day Done window, and the field IDs and current values (`PI 26Q4`, `Committed`), plus the note that field names cannot be resolved through the MCP tools. Needs a rebuild to take effect.

lyrathorpe added 1 commit 2026-09-01 10:29:26 +01:00

docs(memory): record what puts a WSP ticket on the Flamingo board

CI / flake (push) Skipped

CI / flake (pull_request) Successful in 1m18s

Details

3a9fbf1a89

Board 411 filters on membership of the "Flamingo - CommittedWork" saved filter
(or the stf-flamingo-help label), with a sub-filter that hides anything whose
fixVersion is already released. Team, PI and PI Commitment have no bearing on it:
of the filter's 100 most recent members, 52 carry no Team and 94 no commitment.

Records the field IDs and current values anyway, since they are set as a matter
of course for PI planning, and notes that field names cannot be resolved through
the MCP tools.

lyrathorpe scheduled this pull request to auto merge when all checks succeed 2026-09-01 10:30:08 +01:00

lyrathorpe merged commit e2184c601a into main

2026-09-01 10:30:51 +01:00

lyrathorpe deleted branch docs/memory-flamingo-board

2026-09-01 10:30:52 +01:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: lyrathorpe/nixfiles#114