refactor: update work item statuses and sprint planning details for PDIAP-15836 and PDIAP-12284

This commit is contained in:
2026-05-05 16:09:48 -06:00
parent 2a234701c5
commit e4b39c4a9e
5 changed files with 9 additions and 6 deletions

View File

@@ -33,7 +33,8 @@ tags:
- Jeff initially noted that starting this work now could create a long-lived branch, because UIKit-removal work needs feature flags, consumer testing, and a later merge/release window after the REST transition finishes.
- David clarified that the spike identified and documented the root cause, but no code changes have been published yet.
- `PDIAP-12284` is the original UIKit-wrapping removal story and was reopened after rollback. David noted `PDIAP-15836` should be treated as blocked by `PDIAP-12284`, although the Jira link was not yet present.
- Jeff later asked David to start working on `PDIAP-15836` / `PDIAP-12284`, but not to move the stories to In Progress until the next sprint starts on Thursday after lunch.
- Jeff later asked David to start working on `PDIAP-15836` / `PDIAP-12284`, but not to move the stories to In Progress until the next sprint starts on Thursday.
- Quy had already moved the stories into the next sprint (`26Q2.6`); David will leave them in To Do until the sprint starts.
- Jeff's branch-management guidance: after implementation, maintain the branch until consumer-testing approval; merge the GraphQL-removal branch first after the REST validation period, then merge that into the `PDIAP-15836` / `PDIAP-12284` branch. Expected merge timing is roughly 90-100 days from today unless Fidelity shortens the review windows.
- Backlog triage