ERM Sprint 70
Sprint Goal / Focus
User configuration
Carried Over: File import; Export
Sprint Schedule
Sprint: 70
Quarter: 2019 Q2
Start Monday 12 Aug, 2pm UK
Finish Friday 23 Aug, 12pm UK
Sprint Capacity
Team Availability: Schedule
Notes / Exceptions:
@steve.osguthorpe available Thu 15 / Fri 16 only
@Owen Stephens not available second week of sprint
Lead Roles:
Front End Code Review: @md331 (Deactivated)
Back End Code Review: @Ian Ibbotson (Use this one)
QA: @Gill Osguthorpe
QA Environment: folio-testing
Sprint Planning
- not in sprint
or @ - in sprint
Sprint Goals
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
|---|---|---|---|
@md331 (Deactivated) | BE: 0h FE: 24h Bulk loader uses controllers directly, so no direct database changes. Script should exist with appropriate end points. | ||
@Claudia Malzer | Requires ERM-389. refData picklister controller already exists. Need to protect some system-level categories (UXPROD-1977). May need some exploratory work to see if controlled vocab can be done.
Work required to create categories. | ||
@Claudia Malzer | Expect PR to come with ERM-390. More straightforward, so start with this before ERM-390. | ||
@Aditya matukumalli | . How best to QA? How do I know that the settings are being applied as expected?
@Owen Stephensand @steve.osguthorpe to confer on most useful approach Aug 16, 2019 @Gill Osguthorpe to provide mockup initially. Probably implement with field arrays. @steve.osguthorpe to dig out endpoints | ||
@John Fereira | JSON part of this is resolved by ERM-385. KBART fix should be able to reuse ERM-385 code. Expected today. | ||
@John Fereira | Populate numFirst(volume), numLast(volume) issues required. Test code exists. Expected today. | ||
https://folio-org.atlassian.net/browse/ERM-356 / https://folio-org.atlassian.net/browse/ERM-361 | @John Fereira | Difficulty is in pulling in the license (or agreement), ie a resource from another module. | |
| @John Fereira | To follow https://folio-org.atlassian.net/browse/UXPROD-1517 issues @Jag Goraya to set up stories for related scenarios Aug 14, 2019 . |
Carried Over
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
|---|---|---|---|
https://folio-org.atlassian.net/browse/ERM-217 / https://folio-org.atlassian.net/browse/ERM-337 | @Aditya matukumalli |
Front-end integration tests (ERM-351) still waiting on STCOM updates. | |
https://folio-org.atlassian.net/browse/ERM-217 / https://folio-org.atlassian.net/browse/ERM-349 | @steve.osguthorpe | Expected today to unblock ERM-337 integration. | |
@steve.osguthorpe | To follow ERM-349. | ||
@steve.osguthorpe | To follow ERM-349. |