Page History

• Attendees / Apologies
• Upcoming Availability

Consistent Dev Environment

Aditya matukumalli to add workspace setup guide to ensure consistency in local test & development environments

Release Candidates

Code Review: 

QA / UAT 

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1239

  /

  Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1240

   
  • Jsut passed
  • Ready for QA pending testing refresh 

For Release

• NA

Items at Risk / Spillover

In Progress

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1241

  • Some cleanup work done in shared component
  • Almost complete 
  • Re-running local tests and then ready for code review
  • Some EOL discrepancies resulting in apparently empty diffs when converting between EOL types

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1527

  • Changes requested from code review
  • Now getting Jenkins errors
    • Seem unrelated to submitted code
    • appears that Jenkins is overloaded
  • Should be able to re-run via PR fail message > details link
    • will take to Jenkins login 
    • from which to trigger refresh
  • Adi to reach out to John Malconian to get Jenkins access for ERM repositories for Peter 
  • In the meantime, refresh has allowed this to get pushed through to Code ReviewPR expected this morning
• RTL Test Conversion:

  • • Jira
      server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1473

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-15311534

  /

  Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-15321531

   
  • need to be merged together
  • some back and forth to get this done in functional logic
  • hooks not working nicely with old REACT methods
  • the changes so far are good enough
  • Adi to set up refactor holding issue in Jira to hook functional logic related techdebt issues
    • labels: erm, techdebt, functional-logic

    • Jira
      server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM

  -1534

  • • -1548

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1532

  • cannot be merged yet because tests are failing locally
   

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1539

  • started to look at this
  • code located and looks straightforward
  • expect to complete Thursday

Sprint Backlog

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1546

  • part the one
    • endpoint set up for myDashboards
    • checks okapi patron login to resolve or create a proxy user 
    • from there can access dashboard objects
  • part the two:
    • widgetType domain class, generic widgetDefinition,  simple widget classes written
  • process for adding in the future 
    • validate imported definition json against standard widget definition
    • then validates definition within json 
  • next: hook widget instance and wire the two parts together

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1538

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1544

Needs Elaboration

New Issues

Added to sprint