/
ERM Sprint 125

ERM Sprint 125

Oct 20, 2021

Sprint Goal / Focus

  • Improvements to Entitlement Log

  • Dashboard UI

Sprint Schedule

  • Sprint: 125

    • Start Mon 11 Oct

    • Finish Fri 22 Oct

    • Sprint Board

    • Jira Sprint: 1040

  • 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:

  • 11-12 Oct: Ethan on leave

  • 11-15 Oct: Ian on leave

  • 13 Oct: Adi 0.5d

  • 15 Oct: Peter not on ERM

  • 18 Oct: Adi 0.5d

  • 21-22 Oct: Adi on leave

  • 22 Oct: Peter not on ERM

Lead Roles:

  • Front End Code Review: @Aditya matukumalli

  • 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

    • environment: local | testing | snapshot | other

    • data

    • scripts

  • 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-3335

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

@Peter Böhm

  • Approach

    • Improve usability of kb

  • Components and Changes

    • Frontend: none

    • Backend: mod-agreements ResourceController

  • Tests / Data: none

  • Dependencies: none

  • Known Unknowns: none

  • QA

    • environment: locally - because of daily title-harvest

    • data: set up a harvest for title-only data

  • Development Estimate: 2d

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

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

@Owen Stephens

  • Approach: 

    • Complete review for user story gap analysis

    • New stories to be added for Lotus as needed

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

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

@Ethan Freestone

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

https://folio-org.atlassian.net/browse/ERM-1884 / https://folio-org.atlassian.net/browse/ERM-1900

@Ethan Freestone

  • Approach

    • suppress entry needs to be persisted on entitlement log

    • update between timed runs would not be caught

  • Components and Changes

    • Frontend

    • Backend: Update logic to handle suppressed fields in mod-agreements

  • Tests / Data: none

  • Dependencies: 

    • need some kind of infrastructure to support recording when a field on a resource is changed

  • Known Unknowns: no

  • QA

    • environment: local | testing | snapshot | other

    • data

    • scripts

  • Development Estimate: <1d

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

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

@Ethan Freestone

  • Approach: 

    • see slack notes

    • @Ian Ibbotson (Use this one)to supplement notes / flesh out subtasks

    • @Ethan Freestoneto carry out development

  • Components and Changes

  • Tests

  • Data

  • Dependencies

  • Known Unknowns

  • QA

    • environment: local | testing | snapshot | other

    • data

    • scripts

  • Development Estimate

 

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

@Aditya matukumalli

  • Approach

    • ERM-1889 Create re-usable status component

    • The newly displayed fields are not editable - hence new component needed, similar to agreements meta

    • existing meta section component in FOLIO is not suitable

  • Components and Changes

    • Frontend:

      • stripes-erm-components:

        • set up stripes-erm-components for RTL tests

        • add new component for metadata status

        • add styling (reuse from meta section)

        • support dynamic fields as children prop

        • add translation support for dynamic fields

        • render as an accordian (re-use from stripes-components)

        • pass first line as accordian label prop

        • verify inherited accessibility treatment

      • ui-local-kb-admin: 

        • set up ui-local-kb-admin for RTL tests

        • add translation keys for labels

        • always render the component

        • add display logic to externalDataSourcesView.js

    • Backend: none

  • Tests:

    • ui-local-kb-admin

    • stripes-erm-components

  • Data: no

  • Dependencies: none

  • Known Unknowns:

    • name of component

  • QA

    • environment: snapshot

  • Development Estimate

    • status component: 2d

    • lkb: 2d

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

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

@Claudia Malzer

@Aditya matukumalli

  • Approach

    • Add validation to FieldArray  - already in place

    • Check field meta, such as whether it is touched (as opposed to dirty)

    • Compare with how similar is handled with overlapping dates

    • Recent changes

      • ERM-1826

      • ERM-1688 - autofocus behaviour changed to now remains on Add Column, which means validation doesn't fire (only fires on touched fields)

  • Components and Changes

    • Frontend: ui-dashboard

    • Backend: none

  • Tests / Data / Dependencies: 

    • Adi to Fix Save and Close on issue

    • Ethan to verify consistency of validation pattern 

  • Known Unknowns

    • FieldArray validation already exists, 

    • Not clear why this would be different to other field arrays

  • QA

    • environment: snapshot 

    • data / scripts: no

  • Development Estimate: unknown

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

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

@Claudia Malzer

  • Components and Changes

    • Frontend: ui-dashboard

    • Backend: none

  • Tests/ Data : none

  • Dependencies: none

  • Known Unknowns: none

  • QA: snapshot

  • Development Estimate: <0.5d

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

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

@Claudia Malzer

  • Approach

  • Components and Changes

    • Frontend: ui-dashboard

    • Backend: none

  • Tests/ Data : none

  • Dependencies: none

  • Known Unknowns: none

  • QA: snapshot

  • Development Estimate: <0.5d

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

https://folio-org.atlassian.net/browse/ERM-1467 / https://folio-org.atlassian.net/browse/ERM-1468 / https://folio-org.atlassian.net/browse/ERM-1472

@Monireh Rasouli

  • Approach: RTL Migration

  • Components and Changes

    • Frontend: ui-agreements

    • Backend: none

  • Dependencies: None

  • Known Unknowns: coverage gaps

  • QA: NA

  • 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/FAT-81

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

@Aditya matukumalli

For Code Review

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

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

@Aditya matukumalli

For Code Review

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

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

@Aditya matukumalli

For Code Review

 

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

@Aditya matukumalli

For Code Review

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

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

@Aditya matukumalli

More complex, and to be picked up after simpler tests and feature work: 

This sprint:

 

 

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

@Monireh Rasouli

Issues with adding users to workspace

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

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

@Peter Böhm

Previously TODO:

Planning

  • QA

    • environment: local | testing | snapshot | other

    • data

    • scripts

  • Development Estimate: aim for code review Wed/Thu

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

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

@Ethan Freestone

 

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

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

@Owen Stephens

Additional functionality added for creating print instance. Needs to be re-tested. 

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

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

@Owen Stephens