Page History

...

Time

Item

Notes

<5 mins

Introductions

Attendees / Apologies
Upcoming Availability

Previous Actions

NA

5 mins

In Review

Any impediments to review or QA?
Any useful context, implementation choices or limitations for the reviewer/tester to know ?

Code Review:

NA

QA / UAT

Expected to be Accepted or Closed by time of call

Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1697
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1656
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1774

Bugfix Cycle

NA

WIP

What progress or impediment on previously stated actions?
What's left to do?
What help or input is needed?
When expected to be ready for review?

In Progress

Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1731
- previously
  - Peter adding integration test and modify to test save method - Expected Thus 12th Aug
  - todo: integration tests
  - expected for code review Thu 5 Aug
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1283
- CLOSED
- some code review changes requested
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1802
- Been running v7 1 week - no issues so far - waiting to see what other teams find.
- any issues found with the pre-alpha on ERM modules?
  - if so, log any feedback on issue and send to Stripes/Zak
  - if not, confirm to close by end of week Fri 13 Aug
- any issues reported from other module users that may have an impact on ERM?
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1649
- IN QA by end of 11th Aug
- Previously todo:
  - - run ingests to test changes made locally
    - re-run via master
  - expecting something for QA on Fri 6 Aug
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1787
- Awaiting further feedback from Stripes - move to backlok

Pending

Sprint Backlog

Who is picking up what next?
When is next issue expected to start / complete?
Anything needed to start next issue (dependencies or clarifications)?

Needs Elaboration

Who needs to be involved in the elaboration process?
What is the timeframe for getting input?
When is the issue expected to be ready for development?

Blocked

Are the blocking conditions still relevant?
What action is needed to unblock, and by whom?

Sprint Backlog - Next Up

Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1261
- CLOSED
- expected to be completed by Thu 5 Aug
- what is the next RTL migration target?
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1647
- expected to be closed

Sprint Backlog - to follow

Monireh
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1786
- Expected Ready for code review 11th Aug
Peter
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1754
- expect to start Thu 5 11 Aug
Ethan
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1801
- expect to start Mon 9 Thu 11 Aug
Claudia?
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1784
/ CLOSED
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1785
CLOSED

Needs Elaboration

Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1648
- Accessibility testing is complete and all feedback from users is in.What action or change, if any, is needed based on this?
- Gill to talk to Adi and Ethan

Blocked

Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1775
- waiting on ERM-1731- completed 12th Aug

At Risk

What is now at risk of not being started this sprint?
Do any of these take priority over other sprint backlog items?

Sprint Backlog

Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1798
- Won't get started this sprint
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-506
- Peter to look to see if it is something he can pick up
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1797
- Not going to be started
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1799
- Ethan priority after next issue - unlikely to be started
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1788
- Claudia started - carry over to next sprint - no support needed currently.

Release Candidates

What has passed QA since last dev call?
What has been closed since last dev call?

Accepted

Closed

Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1767
RTL
- Jira
  server FOLIO Issue Tracker
  serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
  key ERM-1379
- Jira
  server FOLIO Issue Tracker
  serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
  key ERM-1372
- Jira
  server FOLIO Issue Tracker
  serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
  key ERM-1380
- Jira
  server FOLIO Issue Tracker
  serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
  key ERM-1360
- Jira
  server FOLIO Issue Tracker
  serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
  key ERM-1370

<10 mins

AOB

New Issues

Added to sprint

Assigned ERM-1258 to MR
Adi to pick some issues from
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key FAT-81
and move into sprint

NA.
Readme notes added to mod-agreements / devops - Steve followed up on Slack.

Not added to sprint

NA

Space shortcuts

Child pages

Versions Compared

Old Version 2

New Version Current

Key

Code Review:

QA / UAT

Bugfix Cycle

Sprint Backlog - Next Up

Sprint Backlog - to follow

Needs Elaboration

Blocked

At Risk

Sprint Backlog

Release Candidates

New Issues