docs(memory): record what puts a WSP ticket on the Flamingo board
CI / flake (push) Skipped
CI / flake (pull_request) Successful in 1m18s

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.
This commit is contained in:
Emma Thorpe
2026-09-01 09:58:49 +01:00
parent 7ab3071ea9
commit 3a9fbf1a89
2 changed files with 41 additions and 0 deletions
+1
View File
@@ -17,3 +17,4 @@
- [WSP local build and test](wsp_local_build_and_test.md) — core-services-cloud on this box: dotnet via nix, artifactory creds from `~/.artifactoryenv` sourced per command, how to tell auth failure from a code failure
- [WSP-32957 PIM migration](wsp_32957_pim_migration.md) — AKS RBAC to PIM + AutoPerm decommission; prod is in the Technical Preview subscription, three tenants; resume via `~/code/WSP-32957-CONTINUATION.md`
- [Entra group member reads](entra_group_member_reads.md) — `az ad group member list` hides service principal members; use the servicePrincipal cast or transitiveMemberOf, and trust the Terraform plan over it
- [Flamingo Jira board](jira_flamingo_board.md) — board 411 needs `Flamingo - CommittedWork` membership and an empty/unreleased fixVersion; Team/PI/Commitment do not affect it