/
2020-04-01 ERM Weekly Delivery Update

2020-04-01 ERM Weekly Delivery Update

Apr 01, 2020

Meeting Details

Date
 
Time

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

LocationVideo Call in FOLIO Slack: #erm-developers

Participants

Apologies

Discussion items

Time

Item

Notes

Action Items

<5 minsIntroductions


20 minsSprint Cutoff

Release Candidates

  • Code Review: 

    • NA

  • QA / UAT: should all be testable Wed/Thu

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

    • ERM-785 - Getting issue details... STATUS
    • ERM-553 - Getting issue details... STATUS
    • ERM-705 - Getting issue details... STATUS
    • ERM-735 - Getting issue details... STATUS
    • ERM-781 - Getting issue details... STATUS
    • ERM-786 - Getting issue details... STATUS
    • ERM-748 - Getting issue details... STATUS  /  ERM-777 - Getting issue details... STATUS  
      • need backend doing
      • pushed back to sprint backlog for Steve
    • ERM-815 - Getting issue details... STATUS
    • LAS:eR:  ERM-750 - Getting issue details... STATUS  /  ERM-700 - Getting issue details... STATUS  /  ERM-702 - Getting issue details... STATUS  /  ERM-763 - Getting issue details... STATUS
      • demo last week
      • acceptance criteria document complete
      • being used to define remaining tasks to complete
      • approx 1-2 days dev expected (to be picked up by Ethan)
      • Owen to test locally at the moment (~1hr)
      • Unclear whether GBV/HBz will do their own UAT

Items at Risk / Spillover

  • In Progress
    • ERM-547 - Getting issue details... STATUS
      • filter added to package ingest - needs local testing 
      • then code review
    • ERM-793 - Getting issue details... STATUS
      • sidetracked by laser
      • Ethan to push branch for Peter to pickup
      • mod-agreements: has a bunch of TODOs that may help
    • ERM-805 - Getting issue details... STATUS
      • embargo component created, being called from coverage component
      • is that right? could do with solution design review before committing
      • branch is pushed
  • Open / Sprint Backlog
    • ERM-788 - Getting issue details... STATUS
      • Owen and Steve to talk Thu 2 Apr (11am)
    • ERM-794 - Getting issue details... STATUS  /  ERM-795 - Getting issue details... STATUS
    • ERM-800 - Getting issue details... STATUS
  • Needs Elaboration
    • ERM-797 - Getting issue details... STATUS  /  ERM-798 - Getting issue details... STATUS  /  ERM-801 - Getting issue details... STATUS  /  ERM-803 - Getting issue details... STATUS  /  ERM-796 - Getting issue details... STATUS
      • Technical not viable at this stage
      • Agreed with Leipzig to descope for Goldenrod
      • Moved out of sprint
      • Medium-term priority still TBC
    • ERM-807 - Getting issue details... STATUS
  •  

15 mins

New Issues

Raised: 

  • ERM-810 - Getting issue details... STATUS  - released in ui-licenses 3.7.2
  • ERM-811 - Getting issue details... STATUS  - ready to progress (backend)

Additional:

  • displaying picklist values in edit picklist UI to ensure amended value is as expected
  • Owen to draft story for Adi to pick up while working in this area

10 mins

Next Sprint

ERM-814 - Getting issue details... STATUS


<10 minsAOB

Ready to Progress reviewed/triaged

  • ERM-694 - Getting issue details... STATUS
  • ERM-190 - Getting issue details... STATUS
  • ERM-193 - Getting issue details... STATUS
  • ERM-496 - Getting issue details... STATUS
  • ERM-550 - Getting issue details... STATUS
  • ERM-746 - Getting issue details... STATUS
  • ERM-784 - Getting issue details... STATUS  
    • would Select All be for all items matching query, all on page, or all in progressive view?
    • Export All instead would be similar to LDP
    • If progressing something with similar intent, a discrete Export All option 
    • cannot realistically be done. Owen to close. 
  • ERM-809 - Getting issue details... STATUS  - Mark to pick up
  • ERM-811 - Getting issue details... STATUS

ERM-788 - Getting issue details... STATUS  needs further elaboration


  •