2021-01-12 ERM Weekly Delivery Update

Owned by Jag Goraya
Last updated: Jan 12, 2022

Meeting Details

Date

 

Time

9:05am ET, 2:05pm UK, 3:05pm Germany

Location

Video Call in

Previously2021-12-15 ERM Weekly Delivery Update
ReferencesJIRA Issue Board

Goals

Participants

Apologies

Discussion items

Time

Item

Notes

<5 minsIntroductions

Call Priorities




WIP 

  • What progress or impediment on previously stated actions?
  • What's left to do?
  • Any new unknowns?
  • What help or input is needed?
  • When expected to be ready for review?

In Progress

  • ERM-1850 - Getting issue details... STATUS
  • ERM-1953 - Getting issue details... STATUS
    • moved acqMethods to new folder
    • created new mock and tests
    • tests should be fine, but not mocks with okapiKY (locally)
    • stripes-config in stripes-core
    • TODO
      • get rid of stripes repos locally
      • call stripes-core and -components remotely, not locally
  • ERM-1973 - Getting issue details... STATUS
    • not able to diagnose
      • resources not being fetched
      • endpoints not being called
    • seems to be when editing and viewing interfaces
      • need to navigate away and then return
    • possible routes:
      • fetch line with hasInterface == 2.0 conditional may need to be TRUE'd 
      • parameters:
        • maybe throwing an error will yield a different fail
        • relies on 
      • permissions check: unlikely unless these changed since implementing (post-Iris, pre-Juniper)
    • if neither, then should seek further input rom stripes
    • Future Option: 
        • move interfaces over to use react-query to fetch data as and when needed, though doesn't address manifest issue, if there is one. NOT to be done now. 

Pending

Blocked

  • Are the blocking conditions still relevant? 
  • What action is needed to unblock, and by whom?

Needs Elaboration

  • Who needs to be involved in the elaboration process? 
  • What is the timeframe for getting input?
  • When is the issue expected to be ready for development?

Sprint Backlog

  • Who is picking up what next?
  • When is next issue expected to start / complete?
  • Anything needed to start next issue (dependencies or clarifications)?

Blocked

  • ERM-1941 - Getting issue details... STATUS
    • effectively blocked by FOLIO-3362 - Getting issue details... STATUS

Needs Elaboration

  • NA

Sprint Backlog - Next Up

  • Claudia:
  • Ethan:
  • Monireh: 
    • backend
    • RTL
  • Peter:  TBD




At Risk

  • What is now at risk of not being started this sprint?
  • Do any of these take priority over other sprint backlog items?

Sprint Backlog - to follow

  • ERM-1923 - Getting issue details... STATUS / ERM-1920 - Getting issue details... STATUS
    • need to go back to verify that this is at ERM end

Sprint Backlog -  At Risk

  • ERM-1938 - Getting issue details... STATUS
  • ERM-1974 - Getting issue details... STATUS
    • has similar technical to ERM-1973

In Review

  • Any impediments to review or QA?
  • Any useful context, implementation choices or limitations for the reviewer/tester to know ?


Code Review: 

QA / UAT 

  • ERM-1931 - Getting issue details... STATUS
    • small change to web-toolkit
    • need to QA issue but also keep an eye on impact on hosted-ref-env, including performance
    • to monitor prior to full release

Bugfix Cycle 

  • NA



Release Candidates

  • What has passed QA since last dev call?
  • What has been closed since last dev call?

Accepted

New

  • NA

Closed: Lotus R1 2022

Features

RTL / Other Tests

<10 mins

AOB


New Issues

Added to sprint

Not added to sprint

  • ERM-1977 - Getting issue details... STATUS
    • closed as Duplicate

Other

GOKb XML Issue

  • is this confirmed fixed?
  • any issue to develop/test going forward?
    • not so much ... more a question of whether we want to present better visibility or failure reporting to devops or other interested users.

GitHub Actions

  • got a GA YAML file based on other modules on a branch for ERM
  • pending merge
  • can run parallel to Jenkins
  • applying to ui-agreements