ERM Sprint 135

Sprint Goal / Focus

  • License Term Management

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 AvailabilitySchedule | Calendar

Notes / Exceptions:

  • NA

Lead Roles:

QA Environment: folio-snapshot

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 Agenda
  1. Sprint Goal / Focus
  2. Sprint Capacity
  3. Review sprint candidates 
  4. Agree technical approach / define key implementation tasks
  5. Finalise estimates / costings
  6. Confirm sprint scope
  7. Confirm first actions





Sprint Planning  

(error) - not in sprint

(tick) 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


ERM-2042 - Getting issue details... STATUS

For Lotus Bugfix 

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

UXPROD-3410 - Getting issue details... STATUS

ERM-2043 - Getting issue details... STATUS

(question)

Ethan Freestone 

To follow ERM-1978 - Getting issue details... STATUS

To be done as extension of ERM-1906 - Getting issue details... STATUS

  • Development Estimate: 20 minutes once 1906 is done

UXPROD-2850 - Getting issue details... STATUS

ERM-2041 - Getting issue details... STATUS

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

UXPROD-2337 - Getting issue details... STATUS

ERM-778 - Getting issue details... STATUS
  • 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

UXPROD-3407 - Getting issue details... STATUS

ERM-2044 - Getting issue details... STATUS

  • 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

UXPROD-3591 - Getting issue details... STATUS

ERM-2045 - Getting issue details... STATUS

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 ERM-2046 - Getting issue details... STATUS
  • 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 IDIssue IDSprint Backlog?

Notes / Estimates / Actions

FAT-82 - Getting issue details... STATUS

ERM-1507 - Getting issue details... STATUS

ERM-1509 - Getting issue details... STATUS

ERM-1510 - Getting issue details... STATUS

In Code Review

UXPROD-3427 - Getting issue details... STATUS

ERM-1979 - Getting issue details... STATUS

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

UXPROD-3581 - Getting issue details... STATUS

ERM-1986 - Getting issue details... STATUS / ERM-1989 - Getting issue details... STATUS