/
ERM Sprint 132

ERM Sprint 132

Jan 31, 2022

Sprint Goal / Focus

  • 4 Feb: Feature Freeze

Sprint Schedule

  • Sprint: 131

    • Start Mon 24 Jan

    • Finish Fri 4 Feb

    • Sprint Board

    • Jira Sprint: 1114

  • Release: 2022.1 Lotus  

    • Sprint 133: Module Release Deadline

      • Backend 16 Feb 2022

      • Frontend 18 Feb 2022

    • Sprint 136: Bugfix Deadline (25 March 2022)

Sprint Capacity

Team Availability: Schedule | Calendar

Notes / Exceptions:

  • 24-28 Jan: Peter on 25% time

  • 24-28 Jan: Monireh off

  • 31 Jan: Claudia off

Lead Roles:

  • Front End Code Review: @Ethan Freestone

  • Back End 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/UXPROD-3172

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

Pending UAT on ERM-1938 (Agreements and AWS)

 

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

@Ethan Freestone 

  • Approach

    • match key doesn't cover anything existing

      • to be addressed later

    • Work on ERM-1986/ERM-1988 API to be progressed alongside this

  • Components and Changes

    • Frontend: 

    • Backend: mod-agreements

  • QA: snapshot

  • Development Estimate

    • 5d including API design from ERM-198

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

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

ERM-1987: @Gill Osguthorpe 

ERM-1988: @Ethan Freestone 

ERM-1989: @Ethan Freestone 

To follow ERM-1800?

  • Approach

    • API to be developed in tandem with ERM-1800

  • Components and Changes

    • Frontend: ui-agreements

    • Backend: mod-agreements

  • Dependencies: 

    • ERM-1980

    • UX Design 

  • Known Unknowns

    • may not be existing patterns for moving in FOLIO

  • QA: snapshot 

  • Development Estimate

    • UI implementation: ~2d

2022-01-31:

  • Done

    • JSON handling set up

    • TitleIdentifier job / queue implemented

  • TODO: 

    • Final tests then push to QA (expected ready 1 Feb)

 

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

@Peter Böhm 

  • Approach

    • each app should do their own, so this would be a PR to ui-organizations

    • pattern in agreements to follow

      • reference to ui-stripes-handler-registry

      • function is setupRegistry

    • only need to submit a PR for the lookup link

  • Components and Changes

    • Frontend: ui-organizations

    • Backend: none

  • Dependencies

    • environment set up for dashboard and organizations

  • Known Unknowns

    • is there a stripes back and forth?

    • check mod-agreements widget definition to get organization resource name to match

  • QA: snapshot

  • Development Estimate

 

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

@Claudia Malzer 

  • Approach

    • can derive link destination to use from titleList.class 

    • avoid hardcoding link in ERM comparison, and use registry instead

      • for example, ui-agreements index has eventHandler fired by dashboard (LOAD-STRIPES-REGISTRY) which then triggers setupRegistry

      • examples in OA and Dashboard

      • documentation: Registry

  • Components and Changes

    • Frontend: ui-agreements

    • Backend: none

  • QA: snapshot

  • Development Estimate




 

 

 

 

 

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/UXPROD-3172

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

@Ian Ibbotson (Use this one) 

Blocked by https://folio-org.atlassian.net/browse/FOLIO-3362

 

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

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

@Ethan Freestone 

 

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

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

@Monireh Rasouli 

May have (but unlikely to be) something to do with virtualising the script

2022-01-31: still using BigTest tests, which is problematic and potentially causing further failure.

TODO: 

 

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

@Monireh Rasouli 

TODO:

  • Reach out to Acquisitions team to see whether they have mitigations or solutions

  • Timebox further effort: 1 day

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

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

 

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

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

@Ethan Freestone 

For Code Review

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

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

@Ethan Freestone 

For Code Review

For QA

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-1982

@Owen Stephens 

 

 

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

@Owen Stephens 

 

 

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

@Owen Stephens 

 

 

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

@Owen Stephens

 

 

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

@Owen Stephens

 

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

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

@Owen Stephens

Some adjustments expected for alternative approach to updating matched keys over time.

  • Some investigation to work out where to step in to process the changes

  • Dev Estimate: 2d

 

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

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

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

@Owen Stephens

@Monireh Rasouli 

2022-01-31 Returning from QA:

  • Same internal contacts render component used that has pattern to be used. 

  • Simpler than internal contacts (no roles, no links) 

 

For Release Prep

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

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

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-1981

@Owen Stephens 

Expected to not be able to host concurrent database sessions. 

 

 

 

 

 

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
Refresh

 

Dashboard

key summary type assignee status components
Refresh

Other

key summary type assignee status components
Refresh