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


Participants

  • @mention a person to add them as an attendee and they will be notified.

Apologies

Discussion items

Time

Item

Notes

Action Items

<5 mins

Introductions

20 mins

Sprint Cutoff

  • Items at Risk / Spillover

    • Open / Sprint Backlog

    • In Progress

  • Release Candidates

    • Code Review

    • QA / UAT


20 mins

WIP Demos

5 minsNext Sprint
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-1755
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-1513
     
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-217
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-1643
     
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-338
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-182
  •  ALL: review and raise questions on key features/sub-tasks/linked tasks ('is defined by') in preparation for sprint planning on Monday 29 Jul

5+

AOB




Sprint Issues

Sprint Board: https://issues.folio.org/secure/RapidBoard.jspa?rapidView=114

Feature ID

Issue ID

Who

Notes / TODO

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1517

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-265


Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1517

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-327

Requires ERM-265

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1517

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-215


Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1517

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-328

Requires ERM-215

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1751

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-273

(tick)


Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1791

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-289

(tick)


Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1513

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-290


Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1791

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-332

Testing blocked until backend completed and merged. 


Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-276

Date-time fixes for licenses

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1669

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-306


Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-1681

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-344



Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-322

Aditya matukumalli