Page History

Versions Compared

Old Version 1

changes.mady.by.user Jag Goraya

Saved on Jan 08, 2020

compared with

New Version Current

changes.mady.by.user Jag Goraya

Saved on Jan 08, 2020

Key

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

Meeting Details

Date	08 Jan 2020
Time	09:30am ET, 2:30pm UK, 3:30pm Germany
Location	Video Call in FOLIO Slack: #erm-developers

Participants

Apologies

Owen Stephens

Discussion items

Time

Item

Notes

Action Items

<5 mins

Introductions

Attendees / Apologies
Upcoming Availability

20 mins

Sprint Cutoff

Release Candidates
- Code Review - NA
  - Jira
    server FOLIO Issue Tracker
    serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
    key ERM-629
- QA / UAT
  - Jira
    server FOLIO Issue Tracker
    serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
    key ERM-437
  - Jira
    server FOLIO Issue Tracker
    serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
    key ERM-539
  - Jira
    server FOLIO Issue Tracker
    serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
    key ERM-571
Items at Risk / Spillover
- Open / Sprint Backlog - NA
  - Jira
    server FOLIO Issue Tracker
    serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
    key ERM-633
    - expected start this sprint, but to spill over
  - Jira
    server FOLIO Issue Tracker
    serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
    key ERM-640
    - reassigned from Ethan Freestone to Aditya matukumalli (because reshare)
  - Jira
    server FOLIO Issue Tracker
    serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
    key ERM-434
    - Mark Deutsch to pick up front end to coincide with ERM-644 for QA
- In Progress
  - Jira
    server FOLIO Issue Tracker
    serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
    key ERM-591
    - expected ready for QA Thu
  - Jira
    server FOLIO Issue Tracker
    serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
    key ERM-454
    - issues exposing the right object(?)
  - Jira
    server FOLIO Issue Tracker
    serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
    key ERM-644

15 mins

New Issues

Raised

Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-645
/
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-646
- ERM-646 made subtask of ERM-645, as they will be done together
- Steve Osguthorpe to add summary of agreed approach to parent issue (something along the lines of using js:number and Java:BigInt, which should subsume other numeric requirements)
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-647
- backend to add weight as secondary sort
- added to Ready to Progress
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-649
- what is the better message that's needed? - as per ERM-437
- will be seen during concurrent editing
- added to Ready to Progress - good quick fix
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-650
- to be prioritised against license deletion via UI

Brought into sprint:

NA

10 mins

Next Sprint

TBC. Early quarter focus expected to be around package / content comparison, which is valuable to support renewal decision-making.

<10 mins

AOB

NA