2020-07-01 ERM Weekly Delivery Update

Owned by Jag Goraya
Last updated: Jul 01, 2020

Meeting Details

Date
 
Time

09:30am ET, 2:30pm UK, 3:30pm Germany

LocationVideo Call in FOLIO Slack: #erm-developers

Goals

Participants

Apologies

Discussion items


Time

Item

Notes

Action Items

<5 minsIntroductions


30 minsWIP Updates

Code Review: 

  • ERM-510 - Getting issue details... STATUS

    • works locally now, displaying JSON info as expected
    • progressed to Code Review
    • Owen to create separate story to add the info into UI

In Progress 

  • ERM-950 - Getting issue details... STATUS
    • App is done
    • Tests begun
    • Weird issue re filters: 
      • not showing up in URL
      • Tests seem to block test writing
    • Standalone works
    • Running without ui-agreements runs fine, introducing it causes the filters to not display
    • Two filters with different names = shouldn't be an issue
    • Filters call the plugins, which each call mod-agreements
      • potentially caching some ui-agreements
    • Set up as with other 
    • datakey is being passed in, though needs to be unique
      • may be the same that's being passed in on both filters. 
    • needs a separate endpoint which will be used by ERM-951
  • ERM-951 - Getting issue details... STATUS
    • depends on backend of ERM-950 being merged
    • however there is a PR build failrure because of 
    • JSON structure is not confirmed to be being returned
    • has some dummy data being passed to MCL resembling ERM-953 wireframes
    • frontend work required: 
      • need callback properties in MCL 
      • awaiting shape from ERM-959: added sample during call
    • assume it is data.endpoint
    • will need a STCOM PR 
      • probably ready today
    • will continue to work off Ethan's branch locally

Sprint Backlog

  • ERM-952 - Getting issue details... STATUS
  • ERM-943 - Getting issue details... STATUS  /  ERM-944 - Getting issue details... STATUS  /  ERM-945 - Getting issue details... STATUS
    • Steve has reviewed Ian's preferred approach (extend refdata to include subtype detail), and there is a track-stopping challenge
    • Second property field will be ugly but probably the better approach for now than refdata extension
    • Semantically correct way will surpass sprint boundaries; 
    • Decision on way forward confirmed during call:
      • add second property
    • Allocated to Claudia Malzer
  • ERM-974 - Getting issue details... STATUS  /  ERM-975 - Getting issue details... STATUS
  • ERM-952
    • ERM-957 - Getting issue details... STATUS  - done and committed
    • ERM-959 - Getting issue details... STATUS  - Ethan to add shape for 

Needs Elaboration

  • NA

QA / UAT: 

  • ERM-888 - Getting issue details... STATUS
    • Passed straight through to QA
  • ERM-974 - Getting issue details... STATUS  /  ERM-975 - Getting issue details... STATUS
    • Permission changed from organization-storage to organization
    • causes a breaking interface dependency change
    • Will need to trigger a bugfix release
  •  

10 mins

New Issues

Raised / to bring into sprint: NA

Raised: 

  • ERM-976 - Getting issue details... STATUS  
    • raised as mitigation for ERM-974 and ERM-975
    • brings into line with similar user feedback behaviour introduced for PO lines
    • not required for Goldenrod
    • should be available for Ready to Progress 

<15 minsAOB

NA