lyrathorpe/nixfiles
1
0
Fork 0
Code Issues 6 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

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

Browse Source 
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
Download Patch File Download Diff File Expand all files Collapse all files
home/claude/memory/jira_flamingo_board.md
+40
View File
@@ -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]].