Why: Prokopovych will disband once Orchid is released. A new team(s) must be assigned to own/release inventory modules.

Plan: Spitfire and Folijet co-own modules and backlog

Transition date: Orchid GA date

Responsible for Orchid hotfix/service patch: Yes

Poppy expectations:

No new functionality.
Developers' focus is on acquiring knowledge especially around the release process with so many contributors.
QA's focus is on acquiring knowledge and defining a plan for managing these additional modules/workflows.
PO's focus is on reviewing backlog and evaluating work for Q and R releases
Only address P1 issues and if possible P2.
May need to address MODINVSTOR-960 - Getting issue details... STATUS but details are unclear.

module	New Owner	Support
mod-inventory	Folijet	Marc Johnson
mod-inventory-storage	Spitfire	Marc Johnson

module	New Owner	Support
ui-inventory	Folijet	Michal Kuklis (will be available until June 30 to help with release)
ui-plugin-find-instance	Spitfire	Michal Kuklis (will be available until June 30 to help with release)
ui-plugin-create-inventory-records	Folijet	Michal Kuklis (will be available until June 30 to help with release)

Prokopovych unclosed epics: Getting issues... (2)
Prokopovych unclosed features: Getting issues... (94)
Prokopovych unclosed issues (no epics, umbrellas, new features) - note that this includes ALL modules, not just Inventory-related ones: https://folio-org.atlassian.net/issues/?filter=15187 (449)
- P1/P2 issues (21 issues)
- P3/P4 issues (245 issues)
- TBD/None issues (177 issues)
Prokopovych unclosed Inventory issues (no epics, umbrellas, new features): https://folio-org.atlassian.net/issues/?filter=15188 (396)
Prokopovych unclosed Inventory bugs (no epics, umbrellas, new features): https://folio-org.atlassian.net/issues/?filter=15189 (36)

Spitfire

Folijet

What additional help is needed to make this transition go smoothly?
1. Folijet: 1 Backend developer (what level? - Kate will make recommendation) | Frontend developer (what level? - Ivan will make recommendation): TBD based on RTL/Jest conversation | TBD : Manual QA? | TBD : AQA
2. Spitfire: TBD : Manual QA? | TBD : AQA
Confirm Karate tests coverage – speak with Marc
What about RTL/JEST remaining work?
1. NES still working on it? What do we need to do?

QA to do (meeting on 3 May)
1. Transition AQA test cases (Natalia and Ivan can schedule a meeting to discuss plan)
2. Transition Jenkins test failure messages (still appearing in Prok Slack channel)
3. QAs: Transition manual QA test cases in TestRail (Natalia and Ivan can schedule a meeting to discuss plan)
4. Review remaining Prok Jest test
5. Review remaining E2E Smoke, Critical Path tests to automate
6. Reassign Karate tests to Spitfire and Folijet
KG: Communicate change to community
KG: Address the RTL/Jest situation with LeeB.
KG/AMB: Review P1/P2 Prokopovych issues
AMB: will come up with a plan for backlog organization
KG/AMB/CSR: reassign features and epics
Each team review Poppy features capacity based on #5. Possibly create another feature for this work.

Browser not supported