Skip to end of banner
Go to start of banner

2019-09-25 ERM Weekly Delivery Update

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Meeting Details

Date 
Time

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

LocationVideo Call in FOLIO Slack: #erm-developers



Apologies

Discussion items

Time

Item

Notes

Action Items

<5 minsIntroductions
  •  
5 minsPrevious Actions
  • Draft Jira issue for the JSON documentation outputs

30 mins

WIP Updates
  • Pending Review
  • In Progress: what's left to do?
    • ERM-457 - Getting issue details... STATUS
      • conversations with dev and PO realising how complex the queries are
      • Owen Stephens defining priority test cases to help with development
      • most complex case is agreement resources, and that's nearly done
      • expected ahead of Claudia starting work on related issues (Thu)
    • ERM-392 - Getting issue details... STATUS  
      • does not require a local frontend
  • Pending: 
    • what's dependent?
      • ERM-466 backend is predecessor for ERM-467 and ERM-468
      • ERM-465 - Getting issue details... STATUS  
        • Reason for Closure is select dropdown rather than modal
        • Refdata needs migration work also
    • what's clear to proceed?
      • ERM-462 - Getting issue details... STATUS  should be ready for QA
  • ERM-465 - Getting issue details... STATUS  Gill Osguthorpe to mockup wireframe for re-jig of heading fields and Reason for Closure select, including both edit and preview

10 mins

New Issues
  • ERM-471 - Getting issue details... STATUS
    • resolved as part of 3.2 bugfix
  • ERM-469 - Getting issue details... STATUS
    • pending elaboration
  • ERM-472 - Getting issue details... STATUS



<10 minsAOB
  • Memory / Timeout Issues on snapshot-stable
    • Test environment is 30s vs 1s locally for retrieving endpoints for entitlement  and entitlement-options  (front and back end)
    • Impact: 
      • testing failure results are ambiguous
      • cannot investigate current process for feature elaboration
      • No way to add an agreement, except by Create an environment
      • backend resource drain / distraction
    • Ian Hardy at IndexData is looking at this with Steve
    • Related Jira issue may have been closed 
    • gbv-intern and gbv-demo are both out-of-date - can be updated?
  • Sprint Planning Calls & Mid-Sprint Planning Calls
  • MCL Column Resizing issue has been raised and pushed back to ERM. STCOM-586. STCOM-586 - Getting issue details... STATUS

Memory / Timeout Issues

  • Prioritise: endpoint development work ahead of timeout resolution

MCL Colum Resizing

  • No labels