ERM Sprint 135
Sprint Goal / Focus
License Term Management
Sprint Schedule
Sprint: 135
Start Mon 7 Mar
Finish Fri 18 Mar
Jira Sprint: 1214
Release: 2022.2 Morning Glory
Sprint 142: Module Release Deadline
Backend 22 June 2022
Frontend 24 June 2022
Sprint 145: Bugfix Deadline (29 July 2022)
Planning Questions
Does the issue meet the criteria for Definition of Ready?
What front and back end components are affected?
What changes need to be made? (additions, removals or modifications)
What development tests need to be written?
What data does the developer need to verify their work?
What are the known unknowns?
What is needed to QA? (environment, data, scripts)
Navigation
Sprint Planning
- not in sprint
or @ - in sprint
Planning Notes Template
Approach
Components and Changes
Frontend
Backend
Tests / Data
Dependencies
Known Unknowns
QA: local | testing | snapshot | other
Development Estimate
Sprint Focus
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
|---|---|---|---|
| @Ian Ibbotson (Use this one) | For Lotus Bugfix In Progress: https://github.com/folio-org/mod-agreements/tree/fix-clone-agreement | |
@Ethan Freestone | To follow https://folio-org.atlassian.net/browse/ERM-1978 To be done as extension of https://folio-org.atlassian.net/browse/ERM-1906
| ||
| |||
@Ethan Freestone
|
| ||
@Ethan Freestone |
| ||
@Peter Böhm | Preparatory work for surfacing external package data in Agreements. Refdata values are based on Gokb, but these are platform neutral More complex are package identifiers (likely to be namespaced)
|
Rolled Over From Previous Sprint
For Development
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
|---|---|---|---|
https://folio-org.atlassian.net/browse/ERM-1507 | @Ethan Freestone | In Code Review | |
@Claudia Malzer | Returned to dev to
Switches to agreementsViewRoute manifest, which doesn't have OA context
| ||
https://folio-org.atlassian.net/browse/ERM-1986 / https://folio-org.atlassian.net/browse/ERM-1989 | @Monireh Rasouli | From Slack: Refactoring is done, atm I'm working on displaying the fields, so if I managed to display the right data, I start writing test for the new components. | |
|
| Ethan has messaged Orgs team to address implementation approach. | |
|
|
For QA
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
|---|---|---|---|
|
|
|
|
For Release Prep
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
|---|---|---|---|
|
|
|
|
Bugfix Cycle
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
|---|---|---|---|
|
|
|
|
Brought In
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
|---|---|---|---|
| @Claudia Malzer | Can model around CoverageFieldArray in agreements | |
| @Ethan Freestone |
|
Removed
Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions |
|---|---|---|---|
| Blocked pending stripes-kint-components migration/refactor |