ERM Sprint 82
Sprint Goal / Focus
- Migration / Import / Custom Properties
Sprint Schedule
- Sprint: 82
- Release: Fameflower
- Quarter: 2020 Q1
- Start Monday 27 Jan, 2pm UK
- Finish Friday 7 Feb, 12pm UK
Sprint Capacity
Team Availability: Schedule | Calendar
Notes / Exceptions: NA
Lead Roles:
- Front End Code Review: md331 (Deactivated)
- Back End Code Review: steve.osguthorpe
- QA: Owen Stephens
QA Environment: folio-testing
Navigation
Sprint Planning
- not in sprint
or @ - in sprint
Brought Forward
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
---|---|---|---|
| |||
In QA | |||
In QA | |||
In QA | |||
In QA | |||
Waiting on completion of ERM-644
| |||
Does need resolving, but not especially urgent. PO decision input from steve.osguthorpe | |||
In QA | |||
In QA | |||
In QA | |||
In QA | |||
In Progress Needs BigTest tests to be written | |||
Higher priority than ERM-647 and ERM-633. Should resolve ERM-427. Workaround: is to manually add JOIN and sort on title of resource. | |||
| Should be resolved by ERM-655. | ||
Sprint Focus
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
---|---|---|---|
Spike: steve.osguthorpe | Custom Properties in this context are like Custom Properties ("terms") in Licenses. Possible conflict of functionality with MOD-CUSTOM-FIELDS (https://github.com/folio-org/mod-custom-fields) Putting into a separate module inhibits searching. TODO:
Front-end implementation with terms is complicated because they are stored as object arrays. | ||
TODO
| |||
Draft UIs defined. Some questions about rules / operations that can be supported. Currently being refined: operator precedence (perhaps some kind of expression grouping. Owen Stephens to merge into ERM-668 and close ERM-684 Has potential relationship to ERM-683. | |||
| Related to service that occurs prior to migrations. Required for live upgrade in second sprint week. | ||
Entitlements package view used to have this problem, but is now fixed. Recent PR related to paging in agreements should help with addressing this. |