ERM Sprint 129

Owned by Jag Goraya
Last updated: Dec 13, 2021
3 min read

Sprint Goal / Focus

  • Remote KB Harvest Sync (Settings)

Sprint Schedule

  • Sprint: 129
    • Start Mon 6 Dec
    • Finish Fri 17 Dec
    • 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:

  • None

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-3337 - Getting issue details... STATUS

UXPROD-3338 - Getting issue details... STATUS

ERM-1906 - Getting issue details... STATUS

ERM-1907 - Getting issue details... STATUS

ERM-1908 - Getting issue details... STATUS

ERM-1909 - Getting issue details... STATUS

ERM-1910 - Getting issue details... STATUS

ERM-1911 - Getting issue details... STATUS

(error)

Needs conversation between Owen and Gill. 

Will push back to new year, which may force a quick fix. 

UXPROD-3339 - Getting issue details... STATUS

ERM-1799 - Getting issue details... STATUS

Peter Böhm 

/ Ethan Freestone 

  • Approach
    • most identifiers are stored on TI, not PCI or PTI
      • this change duplicates it in multiple places
    • add new class (collection of matchkey information) to ermResource abstract class
    • tweak ingest to assign class to PCI and PTI
    • enact this where the entry points converge
      • creation of TIs happens in TitleInstanceResolver -
      • PCI and PTIs are created in a shared process during the ingest
    • store as domain class (matchkey/value string pair) rather than json
  • Components and Changes
    • Frontend: none
    • Backend: mod-agreements
  • Tests / Data
    • won't need to expose through api
    • locally verify with SQL queries to ensure appear in 
  • Dependencies: none
  • Known Unknowns: not yet
  • QA: local vagrant
  • Development Estimate: 

ERM-1923 - Getting issue details... STATUS / 

ERM-1920 - Getting issue details... STATUS
(question)
  • Ethan to refer to Steve

ERM-1948 - Getting issue details... STATUS

Owen Stephens In QA

UXPROD-3338 - Getting issue details... STATUS

ERM-1949 - Getting issue details... STATUS  

ERM-1950 - Getting issue details... STATUS 		Claudia Malzer 
  • 1949: cursor
    • cursor is the change point for differential updates
    • collapse existing buttons to incorporate 
    • reset to null (rather than with value)
  • 1950: syncStatus
    • issue
      • syncStatus has two states (idle or in-process)
      • can sometimes stick at in-process
    • add option to conditionally confirm sync reset for jobs updated over 24 hours earlier
      • date checking within 24 hours: convert difference from milliseconds
    • user needs Settings privileges
  • Components and Changes
    • Frontend:
      • ui-local-kb-admin
    • Backend: none
  • Tests / Data
    • no RTL/JEST or integration tests to be added
    • test locally with, eg, 5 minutes rather than 24 hours
    • use postman to update time via API
  • Dependencies / Known Unknowns : none
  • QA: snapshot 
  • Development Estimate: code review for Wed
FAT-81 - Getting issue details... STATUS

ERM-1484 - Getting issue details... STATUS

ERM-1485 - Getting issue details... STATUS

ERM-1486 - Getting issue details... STATUS

Monireh Rasouli 


UXPROD-3338 - Getting issue details... STATUS


ERM-1922 - Getting issue details... STATUS

Claudia Malzer 

Pending UX input








Rolled Over From Previous Sprint

For Development


Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

FAT-81 - Getting issue details... STATUS

ERM-1483 - Getting issue details... STATUS

Monireh Rasouli 

In Progress

TODO: not seeing the data

FAT-81 - Getting issue details... STATUS

ERM-1480 - Getting issue details... STATUS

Ethan Freestone 

For Code Review

FAT-81 - Getting issue details... STATUS

ERM-1482 - Getting issue details... STATUS

Ethan Freestone 

For Code Review

ERM-1937 - Getting issue details... STATUS

Owen Stephens 

Changed are as expected.

Transferred to QA


ERM-1938 - Getting issue details... STATUS

Owen Stephens 

ERM-1939 - Getting issue details... STATUS

  • Owen to review

ERM-1940 - Getting issue details... STATUS

  • Ethan to progress
  • Approach
    • add controller
    • check regression / translations
  • Components and Changes
    • Frontend: ui-agreements
      • settings index
      • translations
    • Backend: mod-agreements
      • expose Controller 
  • Tests / Data
    • stripes-kint-component
  • Dependencies: none
  • Known Unknowns: 
    • not been unit/integration tested before, so current is unknown
  • QA: snapshot 
  • Development Estimate: Thu or Mon 

ERM-1850 - Getting issue details... STATUS

Peter Böhm 

Reviewed example with Ethan

Vagrant issues

Making progress on subquery

Expected for code review end of Wednesday

No dependencies




ERM-1912 - Getting issue details... STATUS

Peter Böhm 

Test Approach: 

  • Source data has been fixed, so testing without faking the data is going to be problematic (faking or proxying)
  • Set internal value to empty
  • TODO: run integration tests
  • QA: regression test 

 ERM-1921 - Getting issue details... STATUS

Claudia Malzer 

Complete, but not raised as done as part of 1922

Will separate into new branch for code review today.


ERM-1904 - Getting issue details... STATUS

(error)Pending input from Ian

ERM-1922 - Getting issue details... STATUS

(error)Pending input from Gill

ERM-1929 - Getting issue details... STATUS

(error)Pending input from Gill

For QA

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


ERM-1927 - Getting issue details... STATUS

Owen Stephens 

Seems unreliable on radio button selection. This is a stripes level issue. 1927 to return to QA. 

TODO: Owen to raise a stripes issue. 


ERM-1926 - Getting issue details... STATUS

Owen Stephens 



ERM-1931 - Getting issue details... STATUS

Owen Stephens 



ERM-1932 - Getting issue details... STATUS

Owen Stephens 



ERM-1900 - Getting issue details... STATUS

Owen Stephens 



ERM-1882 - Getting issue details... STATUS

Owen Stephens 



ERM-1883 - Getting issue details... STATUS

Owen Stephens 



ERM-1884 - Getting issue details... STATUS

Owen Stephens 



ERM-1912 - 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-1953 - Getting issue details... STATUS

Monireh Rasouli 

Remedial work for ERM-1937 - Getting issue details... STATUS

  • Approach
    • add new fetch 
    • filter new fetch based on id
    • provision fallback (show UUID) in case of fetch fail
  • Components and Changes
    • Frontend: ui-agreements
    • Backend
  • Tests / Data
    • tweak test for filters
    • test for fallback
  • Dependencies / Known Unknowns: none
  • QA: snapshot 
  • Development Estimate: code review by Friday

UXPROD-3140 - Getting issue details... STATUS

ERM-1744 - Getting issue details... STATUS

ERM-1745 - Getting issue details... STATUS

Monireh Rasouli 

  • Approach
    • Add json files
    • Trigger type ingest via endpoint / postman
    • Update definition version to 1.1.0
    • Not a breaking change, should just appear in widget config
  • Components and Changes
    • Frontend: none
    • Backend: none
  • Tests / Data: none (would be on ingest process)
  • Dependencies
    • add registry
  • Known Unknowns
  • QA: local + snapshot
    • local: test upgrading
  • Development Estimate: 0.5d

UXPROD-3338 - Getting issue details... STATUS

ERM-1762 - Getting issue details... STATUS

Claudia Malzer 

  • Approach
    • Check if eUsage plugin is present
      • pluggable component returns a data key, rather than module-name
      • so, if pluggable render returns null ... 
    • If not, do not show Usage data accordian
    • Add new Agreement Display setting using mod-config
    • Set default as false (no change to existing behaviour)
    • Applies to Edit screen only
  • Components and Changes
    • Frontend: ui-agreements
    • Backend: none
  • Tests / Data
    • extend settings page tests
    • extend agreement edit page tests
  • Dependencies: none
  • Known Unknowns
    • eusage not working for dev 
  • QA: snapshot 
  • Development Estimate: Wed for code review

Removed

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

UXPROD-3339 - Getting issue details... STATUS

ERM-1799 - Getting issue details... STATUS



UXPROD-3172 - Getting issue details... STATUS

ERM-1929 - Getting issue details... STATUS


Pending UX input



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