Merge pull request 'docs(memory): record what puts a WSP ticket on the Flamingo board' (#114) from docs/memory-flamingo-board into main

Reviewed-on: #114

home/claude/memory/MEMORY.md

@@ -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

home/claude/memory/jira_flamingo_board.md

@@ -0,0 +1,40 @@
+---
+name: jira-flamingo-board
+description: What a WSP ticket needs to appear on the STF Flamingo board (411) — membership of the "Flamingo - CommittedWork" saved filter and no released fixVersion; Team/PI/Commitment do not affect it.
+metadata:
+  node_type: memory
+  type: reference
+---
+
+Board **411** (`https://citrix.atlassian.net/jira/people/712020:adee5450-23f2-4ac7-a208-6851f44b214b/boards/411`), STF Flamingo. Verified 2026-09-01 against the board's own configuration.
+
+**Filter**
+
+```
+(filter = "Flamingo - CommittedWork" AND (statusCategory != Done OR resolutiondate >= -30d))
+  OR (labels = stf-flamingo-help)
+ORDER BY Rank ASC
+```
+
+**Sub-filter:** `fixVersion in unreleasedVersions() OR fixVersion is EMPTY`. Timeframe 2 weeks.
+
+**So a new ticket appears only if both hold:**
+
+1. It is a member of the saved filter `Flamingo - CommittedWork`, **or** carries the label `stf-flamingo-help` (the escape hatch that pulls in WSHELP customer escalations).
+2. Its `fixVersion` is empty or points at an **unreleased** version. A released fixVersion hides the ticket outright, even while it is still In Progress.
+
+Done items drop off 30 days after `resolutiondate`.
+
+**`Flamingo - CommittedWork` is curated, not computed.** Of its 100 most recently updated members, 52 have no Team, 94 have no PI Commitment, and its components span the whole product. Nothing about Team, PI or PI Commitment will get a ticket into it — check membership with `filter = "Flamingo - CommittedWork" AND key = WSP-xxxxx` and add the ticket to the filter if it is missing.
+
+**Set these anyway, per Lyra's house rule** — they drive PI planning and reporting, not the board:
+
+| Field         | ID                  | Value                                                       |
+| ------------- | ------------------- | ----------------------------------------------------------- |
+| Team          | `customfield_10001` | `STF Flamingo` = `8df4e08d-6dd2-4f88-a646-b3f97a089e6c-106` |
+| PI            | `customfield_10322` | current PI, multi-value; `PI 26Q4` = `12824` as of 2026-09  |
+| PI Commitment | `customfield_10095` | `Committed` = `11527` (`Committed After Plan` = `11528`)    |
+
+`Teams` (`customfield_10065`) is a **different, unused** field — leave it alone. Field names are not resolvable through the MCP tools; get IDs from `getJiraIssueTypeMetaWithFields` on the Epic type with `requiredFieldsOnly: false`.
+
+**How to apply:** after creating or closing a WSP ticket for Lyra, confirm filter membership and check `fixVersion` before claiming it will show on the board. Related: [[jira-wsp-fields]], [[jira-tooling]].