Meeting Details

Date	04 Dec 2019
Time	09:30am ET, 2:30pm UK, 3:30pm Germany
Location	Video Call in FOLIO Slack: #erm-developers

Participants

Time

Item

Notes

Action Items

<5 mins

Introductions

5 mins

Previous Actions

NA

20 mins

Pending: what's dependent?
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-297
  /
  Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-352
  - code error presented in dialog box.
  - back to backlog for pickup in next sprint
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-591
  - to pickup in Sprint 78
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-587
  - resolved
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-584

what's dependent? nothing<10 minsAOB

- - blocked by
    Jira Legacy
    server System Jira
    serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
    key ERM-633
In Progress: what's left to do?
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-614
  - PR imminent
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-297
  /
  Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-348
For Review:
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-356
  /
  Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-361
For Release
- https://issues.folio.org/issues/?jql=Sprint%3D362%20and%20status%20%3D%20"In%20QA"

10 mins

Next Pickups

Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-607
Claudia Malzer
Jira Legacy
server

New Issues

System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-461
Peter Böhm
Agreements / New/Edit: Aditya matukumalli
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-612
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-620
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-622
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-624
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-626
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-608
- Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-604
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-633
Ethan Freestone

<10 mins

AOB

Edelweiss Release:

steve.osguthorpe : Back-end modules on track for release this afternoon (after ERM-614 is merged)
md331 (Deactivated) Tests failing for stripes-erm-components , which is delaying remaining front-end modules (ui-licenses , ui-agreements )

Accessibility Review (Gill Osguthorpe ):

how to handle external links: Filip & Khalilah to formalise
list of issues being compiled for triage / dupe-checking before adding to Jira
- https://docs.google.com/spreadsheets/d/1WnQ8uhMBZnw2jeFl50mL18xsuF0RZV23CF6XnuwoulY
- md331 (Deactivated) to scan for known existing issues to avoid Jira duplication