ERM Sprint 146

Owned by Jag Goraya
Last updated: Aug 22, 2022

Sprint Goal / Focus

  • Bugfix Deadline

Sprint Schedule

  • Sprint: 146
  • Release: 2022.2 Morning Glory  
    • Sprint 146: Bugfix Deadline (12 August 2022) [FOLREL-535]
  • Release: 2022.3 Nolana  
    • Sprint 6 of 9 since Release Development Cycle Starts (Sprint 142) to Feature Freeze (Sprint 150)
    • Sprint 151: Module Release Deadline [FOLREL-549]
      • Backend 26 Oct 2022
      • Frontend 28 Oct2022
    • Sprint: Bugfix Release Deadline (2 Dec 2022) [FOLREL-550]

Development Meetings

Sprint Capacity

Team Availability: Schedule | Calendar

Notes / Exceptions:

  • Claudia: 8-12 Aug
  • Owen: 15 Aug - 2 Sep

Lead Roles:

QA Environment: folio-snapshot

Present

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: snapshot | local | testing | other

  • Development Estimate

Sprint Focus

Maintenance

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2133 - Getting issue details... STATUS

Claudia Malzer 


UXPROD-3754 - Getting issue details... STATUS

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2306 - Getting issue details... STATUS

(tick)

Add sibling list property to availabilityScope

  • Approach

    • create as imported
    • store as refData (normalised objects, like packageContentType)
    • add refData to domain model
    • add refData to migrations
    • extend schema and ingest service

  • Components and Changes

    • Frontend: none

    • Backend: mod-agreements

  • Tests / Data: none, use package tests

  • Dependencies

    • required for 2307, 2308, 2309

  • Known Unknowns: none 

  • QA: snapshot

  • Development Estimate: 2d

ERM-2307 - Getting issue details... STATUS

(question)

  • Approach

    • explicitly comment the behaviour /  business rule in the code
    • Add logic (if / elseif) inside adaptor

  • Components and Changes

    • Frontend: none

    • Backend: mod-agreements (adaptor)

  • Tests / Data: none

  • Dependencies: ERM-2306

  • Known Unknowns: none

  • QA: snapshot

  • Development Estimate: == ERM-2311

ERM-2308 - Getting issue details... STATUS

(question)

  • Approach

    • render refdata label as bulleted list
    • use stripes-list component

  • Components and Changes

    • Frontend: ui-agreements

    • Backend: none

  • Tests / Data:

    • adapt availability test using stripes-list interactors

  • Dependencies: ERM-2306

  • Known Unknowns: none

  • QA: snapshot

  • Development Estimate: 0.5d

ERM-2309 - Getting issue details... STATUS

(question) 

  • Approach

    • lookup the refdata
    • query refdata
    • filter on list
    • use selection rather than checkboxes doing lookup
    • publicationType is checkboxes - so, OR'd in filter, rather than AND
    • no default to be set 
    • no lookahead for now

  • Components and Changes

    • Frontend: ui-agreement

    • Backend: none

  • Tests / Data:

    • if we already have existing filter tests

  • Dependencies: ERM-2306

  • Known Unknowns

    • list size may encourage select rather than checkboxes
      • expecting to be in the order of 10s, rather than 100s

  • QA: snapshot 

  • Development Estimate: 1d

ERM-2310 - Getting issue details... STATUS

(question)

  • Approach

    • add new logic to packageIngestService lines 212-218
    • ensure save after block
    • use existing patterns for updating PTI

  • Components and Changes

    • Frontend: none

    • Backend: mod-agreements packageIngestService 

  • Tests / Data: package test data

  • Dependencies: no

  • Known Unknowns: none

  • QA: snapshot 

  • Development Estimate: small