/
ERM Sprint 136

ERM Sprint 136

Apr 03, 2022

Sprint Goal / Focus

Sprint Schedule

  • Sprint: 135

    • Start Mon 21 Mar

    • Finish Fri 1 Apr

    • Sprint Board

    • Jira Sprint: 1215

  • 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 Availability: Schedule | Calendar

Notes / Exceptions:

  • NA

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

ERM-2051: Licenses: primary terms are listed in drop-down for optional terms (Lotus)Closed

@Claudia Malzer 

  • Approach

    • add frontend filter to dropdown for optional properties

  • Components and Changes

    • Frontend: stripes-erm-components

    • Backend: NA

  • Tests / Data: no tests to change

  • Dependencies / Known Unknowns: none

  • QA: bugfest env 

    • may affect both licenses and agreements

    • may need separate dependency bump update for licenses and agreements

  • Development Estimate: unknown

UXPROD-2337: Licenses and Agreements | Support date/time data types for Custom PropertiesClosed

ERM-2048: Add support for Date across Agreement filtersClosed

@Owen Stephens  

Requires Elaboration

Also needs stories for additional Gokb package metadata

UXPROD-3591: Support for enhanced Package metadata in Agreements local KBClosed

ERM-2059: Populate extended Package metadata from GOKb dataClosed

@Owen Stephens 

Requires Elaboration

Also needs stories for additional Gokb package metadata

UXPROD-3591: Support for enhanced Package metadata in Agreements local KBClosed

ERM-2060: Display extended Package metadata in package displayClosed

@Owen Stephens 

Requires Elaboration

Also needs stories for additional Gokb package metadata

UXPROD-3591: Support for enhanced Package metadata in Agreements local KBClosed

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

@Owen Stephens   

Requires Elaboration

Also needs stories for additional Gokb package metadata

 

 

 

 

 

 

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

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

@Claudia Malzer  

 

Unblocked for test development

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 

  • Working on Preview 

  • Approach:

    • Preview: expecting to split out to separate components

    • tests

  • Dev Estimate: + 3d (end of Wednesday)

 

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

 

Ethan has messaged Orgs team to address implementation approach. 

UXPROD-3591: Support for enhanced Package metadata in Agreements local KBClosed

ERM-2045: Extend Package data model to store additional informationClosed

@Peter Böhm 

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)

  • TODO

    • resolve backend issue

      • remove cloneables

      • apply linting and code guidelines

      • check column names are consistently snake_cased

      • set up AlternateResourceName.groovy

    • set up migrations manually 

    • test with temporary endpoint

  • Development Estimate: 

    • Wed 23 for Code Review

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

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

@Ethan Freestone 

  • Approach

    • settings (customPropertiesConfig),

    • edit

    • view (3rd pane in Search and Filter)

    • filters (1st pane in Search and Filter)

  • Components and Changes

    • Backend: web-toolkit-ce, stripes-kint-components

  • Tests / Data

  • Dependencies

    • release of web-toolkit-ce

  • Known Unknowns

    • filter by deprecated values: present them differently 

  • QA: snapshot

  • Development Estimate

    • view: 1d (Mon 21 Mar)

    • filters: 1.5d (Mon 28 Mar)

UXPROD-2337: Licenses and Agreements | Support date/time data types for Custom PropertiesClosed

ERM-778: Add Date type to customPropertiesClosed

 

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

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

@Ethan Freestone

 

 

For QA

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

UXPROD-2337: Licenses and Agreements | Support date/time data types for Custom PropertiesClosed

ERM-778: Add Date type to customPropertiesClosed

 

https://folio-org.atlassian.net/browse/ERM-2017 / https://folio-org.atlassian.net/browse/ERM-2018

@Owen Stephens 

 

For Elaboration

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

@Owen Stephens

GBV discussion on Wed 30 Mar

For Release Prep

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

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

@Owen Stephens 

 

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

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

@Owen Stephens 

 

 

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

@Ethan Freestone 

For Lotus Bugfix

 

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

TBC For Lotus Bugfix / Morning Glory

 

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

@Ethan Freestone 

For Lotus Bugfix

 

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

@Ethan Freestone 

For Lotus Bugfix

 

ERM-2051: Licenses: primary terms are listed in drop-down for optional terms (Lotus)Closed

@Ethan Freestone 

For Lotus Bugfix

 

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) 

Grails compatibliity fix

 

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

 

 

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