Sprint Goal / Focus

License Term MaagementManagement

Sprint Schedule

Sprint: 135
- Start Mon 7 Mar
- Finish Fri 18 Mar
- Sprint Board
- 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)

Sprint Capacity

Team Availability: Schedule | Calendar

Notes / Exceptions:

NA

Lead Roles:

Code Review: Ethan Freestone
QA: Owen Stephens

QA Environment: folio-snapshot

Info

title	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

Table of Contents

Expand

title	Sprint Planning Agenda

Sprint Goal / Focus
Sprint Capacity
Review sprint candidates
Agree technical approach / define key implementation tasks
Finalise estimates / costings
Confirm sprint scope
Confirm first actions

Sprint Planning

- not in sprint

or @ - in sprint

Info

title	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

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-2042

Ian Ibbotson (Use this one)

For Lotus Bugfix

In Progress: https://github.com/folio-org/mod-agreements/tree/fix-clone-agreement

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-3410

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-2043

Ethan Freestone

To follow

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-1978

To be done as extension of

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-1906

Development Estimate: 20 minutes once 1906 is done

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-2850

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-2041

Approach
- some lint changes
- jest-config already exists
- can ignore what is imported from SEC
Components and Changes
- Frontend: stripes-erm-components

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-2337

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-778

Ethan Freestone

Approach
- To be done alongside ERM-2044
Components and Changes
- Frontend: stripes-erm-components
- Backend: web-toolkit-ce
Tests / Data
Dependencies
- release of web-toolkit-ce
Known Unknowns
QA: local | testing | snapshot | other
Development Estimate

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-3407

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-2044

Ethan Freestone

Approach
- To be done alongside ERM-778
- potentially another field
- there are other things that rely on "primary"
Components and Changes
- Backend: web-toolkit-ce, stripes-kint-components
Tests / Data
Dependencies
- release of web-toolkit-ce
Known Unknowns
QA: snapshot
Development Estimate

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-3591

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-2045

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)

Approach
- simple scalar properties
  - content types
  - package availability types (refdata)
  - package lifecycle: (refdata)
  - source data created / updated: (datatype: date (instant), timestamp)
  - description (datatype:
- simple class properties
  - see pattern: agreements alternative names
    - small class with id
  - package content types
  - zero to many alternative names
- ~~zero to many package identifiers~~
Components and Changes
- Frontend: none
- Backend
Tests / Data:
- test with curl
- no integration tests expected until Gokb application done
Dependencies
Known Unknowns
- whether to generalise / extend identifier occurrence or create another one
  - generalising seems overkill and/or wrong-scoping
  - lean towards creating a new version
- package identifier work rescoped to
  Jira Legacy
  server System Jira
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-2046
QA: snapshot via direct API calls
Development Estimate:
- Simple scalar and class: Thursday for Code Review
- ~~Sprint week 2 for package identifiers~~

Rolled Over From Previous Sprint

For Development

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	FAT-82

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-1507

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-1509

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-1510

Ethan Freestone

In Code Review

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-3427

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-1979

Claudia Malzer

Returned to dev to

Revert AgreementsRoute changes
Make no separation between SupplementaryProp and OA properties

Switches to agreementsViewRoute manifest, which doesn't have OA context

something to do with stripes-connect caching?
need to pass datakey as string (second parameter) to compensate for stripes-connect caching

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	UXPROD-3581

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-1986

/

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	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.

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-1958

Ethan has messaged Orgs team to address implementation approach.

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-1297

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

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-1319

Claudia Malzer

Can model around CoverageFieldArray in agreements

Removed

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-1066

Jira Legacy

server	System Jira
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc
key	ERM-2016

Blocked pending stripes-kint-components migration/refactor

Sprint Summary

ERM

Jira Legacy

server	System Jira
columnIds	issuekey,summary,issuetype,assignee,status,components
columns	key,summary,type,assignee,status,components
maximumIssues	20
jqlQuery	labels != release and labels in (licenses, agreements, erm) and Sprint = 1214 and issuetype in standardIssueTypes()
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Dashboard

Jira Legacy

server	System Jira
columnIds	issuekey,summary,issuetype,assignee,status,components
columns	key,summary,type,assignee,status,components
maximumIssues	20
jqlQuery	labels = dashboard and Sprint = 1214
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Other

Jira Legacy

server	System Jira
columnIds	issuekey,summary,issuetype,assignee,status,components
columns	key,summary,type,assignee,status,components
maximumIssues	20
jqlQuery	(labels = release or labels not in (licenses, agreements, erm, dashboard)) and Sprint = 1214
serverId	01505d01-b853-3c2e-90f1-ee9b165564fc

Versions Compared

Old Version 6

New Version 7

Key

Sprint Goal / Focus

Sprint Schedule

Sprint Capacity

Sprint Planning

Sprint Focus

Rolled Over From Previous Sprint

Removed

Sprint Summary

ERM

Dashboard

Other

Page Comparison

Versions Compared

Old Version 6

New Version 7

Key

Sprint Goal / Focus

Sprint Schedule

Sprint Capacity

Sprint Planning

Sprint Focus

Rolled Over From Previous Sprint

Removed

Sprint Summary

ERM

Dashboard

Other