KM: If you create a new feature that is tied to a Roadmap team, please contact a Roadmap team member.
JK: Roadmap team will outline a process for updating the roadmap
JK: Do not need to tie just a UXPROD feature to the Roadmap.
JK: Roadmap goal: Reflect reality consider community/SIG/PO priorities. Inform community when to expect functionality to be released. JK/KM: Provide a tool for the community to see the roadmap and may help to identify resources.
POs' thoughts about the visuals.
Who is the audience? Primary audience: Entry point for anyone to explore FOLIO functionality.
Who contributes to the roadmap?
How to define that a theme is complete?
Action item: Next PO Meeting have Roadmap team join for follow-up questions
Bugfest discussion
15 minutes
Action: Anton will follow up with Dennis regarding ftp limit
In-transit reports - generating csv is failing ( a little less 16k is where the failure occurs)-
BF-259
-
Getting issue details...STATUS
and
CIRC-1485
-
Getting issue details...STATUS
Action item:Charlotte Whitt will unassign from Lotus and move to applicable project and development team
Action item: Add a Lotus release note regarding issue [TBD]
JB: Reference data - > Sending batch notices not working
BF-248
-
Getting issue details...STATUS
Anonymization of Loans: Previous once an hour. Now with Lotus it is inconsistent. Is it module or environment? What is the standard?
Tests failed due to environment limitation - Action item: JB will follow up with testers.
Bugfest is a full-scale environment. It is production ready.
CW: Bugfest data integrity (ex. loan types) - are we testing reality?
Anton start with Day 1 of the previous bugfest
Action item: Anton: Request deployment of Lotus Day1 environment now to help with data clean up to prepare for Morning Glory bugfest. Give more time for POs to review and prepare data.
Action item: Anton will make Release field required for tasks/story/bug/technical debt issue types. No change to the values.