2021-12-08 Product Owner Meetings

Lucy: 

Problem: Charlotte Whitt reported that the FOLIO Snapshot was all in Chinese and reminded development teams of not switching the regular language setting but using the button Change session locale. 

The Shanghai Team confirmed that the Team didn't change the language locale and suggested making changes to the mechanism to avoid such things. Proposed solutions include automatically restoring the settings, adding English translations to the Chinese UI, and more.

There were discussions on Slack. Where did the discussions start in each channel?

#general: https://folio-project.slack.com/archives/C1EPYQKCL/p1638360864102600

#folio-product-council: https://folio-project.slack.com/archives/CTYQZ7PF1/p1638464896149700

#product_owners: https://folio-project.slack.com/archives/G9FUXCJDD/p1638465429138500

Kristin Martin mentioned in the PC channel that CC would work with DevOps to develop some policies and parameters on the public test systems based on the ideas proposed by the Shanghai team.

Options that have been proposed:

• remove diku_admin account and add a user account where invisible permissions can be granted if needed for testing
• create new versions of diku_admin preconfigured for different languages and publicize them - e.g., diku_chinese, diku_russian, diku_german....
• add "change session language" option to the drop down for user profile after login; makes it easier / more accessible to change the session language w/o going to settings
• add a button or some other scripted process to reset the tenant locale periodically 

Some development teams have expressed that they want to have their own logins on the hosted reference environments as well.

• Juniper 
  • Most likely a HF#5 - TBD
• Kiwi is not released (TBD). Hopefully more clarity at tomorrow's 8am ET weekly meeting. 

• Dev Freeze - Jan 28th (core) /  Feb 4th (complete) 
• Sprint 130 | 3 week sprint 
• Dashboard: https://folio-org.atlassian.net/secure/Dashboard.jspa?selectPageId=11847 
• Reminder: User acceptance testing 
• Reminder: Performance/Scalability testing 
  
  • Where do I do this testing? (DB) 
  • Data - Data - Data 
  • Real life use cases 
    • Can we add more details to acceptance tests? 
  • Setting up the tests 
  • Make the system run a marathon
• Testing workshop
  • Include QA testers (per StephB.)

Steph: Title Level Requests going well! Will be done 2/3 development by end of Lotus

Ann-Marie: Folijet - RTL/Jest work will be done this sprint! Also picked up some ui-only stories. After dev freeze deal with bugs. 

Khalilah: Going well. Concern with optimistic locking. 

Upcoming Jira field updates: 

• Root Cause
• Potential Workaround

• Potential Workaround field now displays on issue type = Bug 
• Dennis uses it to display known issues on Release notes - Kiwi (R3 2021) Release Notes#Acquisitions
• Group agrees we should do something similar for Lotus release 
• Ann-Marie > We should document 
• Action item: Dennis will document