Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Meeting Details

Date 
Time

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

LocationVideo Call in FOLIO Slack: #erm-developers



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?
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-457
      • 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)
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-392
       
      • does not require a local frontend
  • Pending: 
    • what's dependent?
      • ERM-466 backend is predecessor for ERM-467 and ERM-468
      • Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyERM-465
         
        • Reason for Closure is select dropdown rather than modal
        • Refdata needs migration work also
    • what's clear to proceed?
      • Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyERM-462
         should be ready for QA
  •  
    Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-465
     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
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-471
    • resolved as part of 3.2 bugfix
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-469
    • pending elaboration
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-472



<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.
    Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keySTCOM-586

Memory / Timeout Issues

  • Prioritise: endpoint development work ahead of timeout resolution

MCL Colum Resizing