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


Apologies

  •  

Discussion items

Time

Item

Notes

Action Items

<5 minsIntroductions
  •   
5 minsPrevious Actions
  • From 2019-10-09 - Steve Osguthorpe to create Jira issue for backend tests for 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-396

Tests to be incorporated as part of normal delivery. Steve Osguthorpeto complete and progress issue.

30 mins

WIP Updates
  • Pending: 
    • what's dependent?
    • what's clear to proceed?
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-356
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-519
      • Depends on 
        Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyERM-528
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-521
       
  • In Progress: what's left to do?
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-459
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-503
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-392
       and 
      Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-393
      • Sticking on 
        Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyERM-404
        : need to check log endpoints
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-457
       and 
      Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-394
       and 
      Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-396
  • Pending Review
  •   

10 mins

New Issues
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-525
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-416
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-454
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-491
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-528
    : prioritised for this sprint
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-530



<10 minsAOB