ERM Sprint 133

Owned by Jag Goraya
Last updated: Feb 14, 2022
2 min read

Sprint Goal / Focus

  • 18 Feb: Feature Freeze

Sprint Schedule

  • Sprint: 133
    • Start Mon 7 Feb
    • Finish Fri 18 Feb
    • Sprint Board
    • Jira Sprint: 1146
  • Release: 2022.1 Lotus  
    • Sprint 134: Module Release Deadline
      • Backend 2 Mar2022
      • Frontend 4 Mar 2022
    • Sprint 137: Bugfix Deadline (8 April 2022)

Sprint Capacity

Team Availability: Schedule | Calendar

Notes / Exceptions:

  • NA

Lead Roles:

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

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

Sprint Focus

Feature ID

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

UXPROD-2850 - Getting issue details... STATUS

ERM-1992 - Getting issue details... STATUS

Monireh Rasouli 

Set up dependencies / libraries for enabling RTL development on

  • ERM Comparisons
  • Plugin Repositories
    • Find License
    • Find Eresource
    • Find Agreement
  • Local KB Admin








Rolled Over From Previous Sprint

For Development


Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


ERM-1990 - Getting issue details... STATUS

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

UXPROD-3335 - Getting issue details... STATUS

ERM-1850 - Getting issue details... STATUS

(error)Push back to Morning Glory release in favour of ERM-1800

ERM-1744 - Getting issue details... STATUS

Monireh Rasouli 



ERM-1745 - Getting issue details... STATUS

Monireh Rasouli 



ERM-1958 - Getting issue details... STATUS

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

ERM-1800 - Getting issue details... STATUS

Ethan Freestone 
  • Approach
    • set up a job
    • look for changed TI / PCI
    • treat matchkey schema as a title instance resolver
    • if potential TI differs, it is changed
    • if an ambiguous match, then log error
      • equivalent case to not ingesting on original load
      • user has option to resolve as they see fit
        • could be updated within ERM
        • more likely, would fix in original kb
  • Components and Changes
    • Frontend: 
    • Backend: mod-agreements
  • QA: snapshot
  • Development Estimate

UXPROD-3339 - Getting issue details... STATUS

ERM-1986 - Getting issue details... STATUS

(error) To follow ERM-1800

ERM-1987: Gill Osguthorpe > Monireh Rasouli  

ERM-1989: Ethan Freestone 


  • Approach
    • API to be developed in tandem with ERM-1800
    • UI
      • add actions button for modal
      • modal has two lookups
  • 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

For QA

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


ERM-1938 - Getting issue details... STATUS

Owen Stephens 



 ERM-1953 - Getting issue details... STATUS

Owen Stephens



ERM-1958 - Getting issue details... STATUS

Owen Stephens



ERM-1923 - Getting issue details... STATUS

Owen Stephens



ERM-1980 - Getting issue details... STATUS

Owen Stephens



ERM-1986 - Getting issue details... STATUS

Owen Stephens


For Release Prep

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions






Bugfix Cycle

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions





Brought In

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


ERM-1999 - Getting issue details... STATUS

Owen Stephens 

  • All table rows are displayed
  • Load More button is missing
  • When it is displayed, clicking Load More does nothing
  • Needs to be checked against earlier release (Kiwi)

May need to be targeted for Kiwi Hotfix Release on 3/4 March

2022-02-14: Regression from list sorting changes


ERM-2000 - Getting issue details... STATUS



Removed

Feature IDIssue IDSprint 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