• Approach
  • fixes initial problem
  • should not appear for title first matching
  • TODO
    • commit changes
    • run against integration tests
    • release
    • add note to migration issue (ERM-1820) to remove  unmapped mitigation
• Components and Changes
  • Frontend: none
  • Backend: mod-agreements
• Tests / Data: none
• Dependencies: none
• Known Unknowns
  • no new instances expected, but any existing anomalies will not be caught
• QA
  • environment: local + snapshot
  • data / scripts: none
• Development Estimate: push to master today

Needs investigation.  

• Approach
  • issue where the component is not being touched
  • TODO check with John Coburn for similar patterns
• Components and Changes
  • Frontend: ui-agreements
  • Backend
• Tests / Data
• Dependencies
• Known Unknowns
• QA
  • environment: local | testing | snapshot | other
  • data / scripts
• Development Estimate

• Approach
  • see comment on https://github.com/folio-org/stripes-components/pull/1617#issue-999577279
  • see readme on readme.md
  • can import defaultKeyboardShortcuts (all) or the appSpecificShortcuts to specify only those required
  • can renamedShortcuts to alter label in specific
    • needs to be translateable string
  • pass renamedShortcuts to shortcuts modal
  • do not need to import copy, cut, paste, find, close, open as they are folio wide and automatically included
• Components and Changes
  • Frontend: components as per issues
  • Backend: none
• Tests / Data: not needed
• Dependencies: none
• Known Unknowns: 
  • can selectively order multiple shortcuts by comma separation
  • shortcuts are ordered as per Guideline 2
• QA: Gill 
  • environment: snapshot 
  • data / scripts: none
• Development 3d. Code Review Wed

• Approach
  • controlled vocabulary has new as part of the component
  • this would be a pattern change, so raises concerns about ux consistency
    • would also get technically messy (switches off some given elements and adds them elsewhere)
  • potentially create a pattern to pass the component through
    • eg, change pane, check pane rendering
  • story needs revisiting: goal is to keep New button visible (not necessarily in top bar)
• Known Unknowns
• TODO: 
  • Owen to revisit story descriptions 
  • Discuss in dev call on Wednesday
    
  • Gill to consider UX options for discussion at mid-sprint review
  • Deferred to Sprint 129 pending UX / Product confirmation

• Approach
  • OS to add test cases
  • mount and update lifecycles of view pane
  • Change to stripes-connector fetches: manual rather than single references because of chunking
  • lengths > 3k characters are failing, rather than 4096 
    • hence limited to 5 concurrent with 60 ids 
• Components and Changes
  • Frontend: ui-agreements
• Tests / Data: none
• Dependencies: none
  • release issue to be created
• Known Unknowns
  • scaling with larger dataset: OS to test
• QA
  • environment: bugfest data, local ui
  • data / scripts: new 1k order line example spread across agreement lines to be set up (eg, 150 POL  x 6 AL)
• Development Estimate:
  • QA and release today