ERM Sprint 138

ERM Sprint 138

Sprint Goal / Focus

Sprint Schedule

Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

  • Peter: on leave except 27-28 Apr

Lead Roles:

  • Code Review: @Ethan Freestone

  • QA: @Owen Stephens 

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

  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  

 - 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

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

 

https://folio-org.atlassian.net/browse/ERM-2076

@Claudia Malzer 

  • Approach:

    • follow wireframe

    • reference can wrap in space as given

  • Components and Changes

    • Frontend: packageCard in ui-agreements

    • Backend: none

  • Tests / Data: extend existing test

  • Dependencies: ERM-2045

  • Known Unknowns

  • QA: local | testing | snapshot | other

  • Development Estimate: 0.5d

https://folio-org.atlassian.net/browse/UXPROD-3591

https://folio-org.atlassian.net/browse/ERM-2046

@Ethan Freestone 

https://folio-org.atlassian.net/browse/ERM-2087

https://folio-org.atlassian.net/browse/ERM-2088

https://folio-org.atlassian.net/browse/ERM-2089

  •  Approach

    • ERM-2087: change identifier occurrence from title to ermResource

    • ERM-2088: follow pattern from ERM-2059

    • ERM-2089: package identifiers (rather than title identifiers) should be overwritten by new assertion (including change of approval state)

    • should be done in ingest rather than adaptor

    • no additional changes needed for KBART

    • migrations

  • Components and Changes

    • Frontend: none

    • Backend: mod-agreements ingest

  • Tests / Data: NA

  • Dependencies: NA

  • Known Unknowns

    • approach: abstract to ermResource (TBC with Ian)

  • QA: snapshot 

  • Development Estimate: Tue 26 Apr

 

https://folio-org.atlassian.net/browse/ERM-2066

@Ethan Freestone

  • Approach

    • strip out stripes-connect in favour of REACT query

  • Components and Changes

    • Frontend: ui-agreements, stripes-erm-components, ui-licenses

    • Backend: none

  • Tests / Data:

    • SEC BigTest migration to RTL

  • Dependencies: NA

  • Known Unknowns: NA

  • QA: snapshot

  • Development Estimate: 3d

 

https://folio-org.atlassian.net/browse/ERM-2081

@Monireh Rasouli 

 

  • Approach

    • implement a widget level prop for isLoading

    • render central spinner if isLoading is true

    • no timeout needed

  • Components and Changes

    • Frontend: ui-dashboard generic 

    • Backend: none

  • Tests / Data: 

  • Dependencies: NA

  • Known Unknowns: NA

  • QA: snapshot 

  • Development Estimate: simple: <2d?

https://folio-org.atlassian.net/browse/FAT-80

https://folio-org.atlassian.net/browse/ERM-1313

@Claudia Malzer 

 

 

Release Tasks - NA

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

 

 

 

 

 

 

 

 

 

 

 

 

 

Rolled Over From Previous Sprint

For Development

 

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

 

https://folio-org.atlassian.net/browse/ERM-2069 / https://folio-org.atlassian.net/browse/ERM-2070 / https://folio-org.atlassian.net/browse/ERM-2071

@Ian Ibbotson (Use this one) 

For Code Review

https://folio-org.atlassian.net/browse/UXPROD-3581

https://folio-org.atlassian.net/browse/ERM-1986 / https://folio-org.atlassian.net/browse/ERM-1989

@Monireh Rasouli

Previous Estimate: 3d (end of Wed 13 Apr)

  • TODO: 

    • Draft PR in place

    • @Ethan Freestone : Investigate potential stripes bug for checkbox / label selection. 

  • Development Estimate: 22 April

 

https://folio-org.atlassian.net/browse/ERM-2060

@Claudia Malzer 

  • Approach

    • MCLs in accordians: don't put fully rendered key value values in here

    • eg, eresources in packages accordian

    • new translation keys: just need to add to en.json 

  • Components and Changes

    • Frontend: ui-agreements

    • Backend: none

  • Tests / Data

    • no sample data yet, but can be added

  • Dependencies

    • ERM-2045: however, can test against the shape of the data, while waiting for 2045 to be merged

  • Known Unknowns

    • Shape is as posted, except contentType TBC (which may become refdata)

    • null value fields:

      • display top level information with "-" as per current behaviour

      • do not show accordian content if null

        • ie, Extended Package Information (eg, description)

        • if accordian would be empty, do not show it

  • QA: snapshot 

  • Development Estimate: Mon 25 Apr

https://folio-org.atlassian.net/browse/UXPROD-3591

https://folio-org.atlassian.net/browse/ERM-2045

@Peter Böhm 

Previous Estimate: 3d (Wed 3 pm end of Wed 23 Mar)

  • Current State

    • hasMany fields expands in package.gson file

    • expansion to ermResource.gson not working

    • contentType from Gokb could be book, journal, database, mixed

      • for now, keep them separate, so switch from string to refdata (array of objects)

  • TODO: 

    • move expansion to ermResource.gson

    • try complete removing Set<AlternateResourceName>

    • otherwise reach out to Steve

  • Development Estimate: 

 

https://folio-org.atlassian.net/browse/ERM-2059

@Peter Böhm 

  • Approach

  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data

  • Dependencies

  • Known Unknowns

  • QA: local | testing | snapshot | other

  • Development Estimate

For QA

For Elaboration

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

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

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

 

 

 

 

Brought In

Removed

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

 

 

 

 

 

 


Sprint Summary

ERM

key summary type assignee status components
Loading...
Refresh

 

Dashboard

key summary type assignee status components
Loading...
Refresh

Other

key summary type assignee status components
Loading...
Refresh