Code for multi-value property has broken single-value properties. 

• Approach
  • Add debug into binding to isolate issue
  • Check each web binding for single and multi-value individually
  • Domain class is exposed by library, so not easy to test in web-toolkit
• Components and Changes
  • Frontend: NA
  • Backend: web-toolkit, dependency bump for mod-licenses, mod-agreements
• Tests / Data: NA
• Dependencies / Known Unknowns: NA
• QA: snapshot 
• Development Estimate: ??

• Approach
  • only GET if there is 
  • hook: useCustomProperties
  • pass enabledProp query parameter to only fire if >1 license
• Components and Changes
  • Frontend: ui-agreements/agreement.js
  • Backend: NA
• Tests / Data: NA
• Dependencies / Known Unknowns: 
• QA: snapshot 
• Development Estimate: 1d

• Approach
  • add callout from stripes-kint-components
  • add default message
  • allow message to be overwritten
  • implement override function to agreements & licenses
• Components and Changes
  • Frontend: stripes-kint-components, ui-agreements, ui-licenses
  • Backend: none
• Tests / Data: no
• Dependencies: required for stripes-kint-components 2.6.0
• Known Unknowns
• QA: snapshot 
• Development Estimate: 1d

• Approach
  • Check refdata is being passed 
  • Check that the issue is happening in other places that refdata is being used (CONFIRMED in licenses)
  • Check that new things are fetched (invalidation is working correctly)
  • Check we're not memo-ising the filter state (such as caching)
  • if we're not caching, where is the update happening (eg, in stripes) > then coordinate to force / trigger a refresh 
• Components and Changes
  • Frontend: agreementFilters
  • Backend: none
• Tests / Data: ?
• Dependencies: ?
• Known Unknowns: may be Stripes / SaS / StripesConnect related
• QA: snapshot
• Development Estimate: ? 

• Approach
  • unlikely to be react, and sure we don't make second fetch for ISSN
  • find the component that is supposed to be rendering
  • if data is there, check shape path
  • if data not there and not in network, check view file on backend
• Components and Changes
  • Frontend: ui-agreements
  • Backend: ? 
• Tests / Data: test the shape still works
• Dependencies / Known Unknowns: 
  • identifier property added at package and title level: shouldn't be an issue as we should not be filtering object by key
• QA: snapshot
• Development Estimate: 0.5d (path) 1d (view) 

• Approach
  • configuration.item.entries.post needed where configuration.item.entries.put is granted 
  • add entry to package.json 
• Components and Changes
  • Frontend: all front-end modules apart from plugins and stripes-*-components
  • Backend: NA
• Tests / Data: NA
• Dependencies / Known Unknowns: NA
• QA: snapshot
• Development Estimate: 1d

• Approach
  • if paging works in places other than agreementLines, then key may be incorrect
  • fetch to mod-config may be using wrong lookup key or parsing out wrong key
  • works for agreements, not resources
    • function may be assuming default location 
    • useAgreementSettings hook
  • use debug to check returned output form lookup
  • use debug to check we are looking in the right place
• Components and Changes
  • Frontend: ui-agreements
  • Backend: NA
• Tests / Data / Dependencies / Known Unknowns: none
• QA: snapshot
• Development Estimate: 1d

• Approach
  • add nullable true constraint to fields in schema
  • (should already be nullable on domain classes)
• Components and Changes
  • Frontend: NA
  • Backend: ermPackageImpl
• Tests / Data: NA
• Dependencies: / Known Unknowns: NA
• QA: snapshot
• Development Estimate: 0.5d

• Approach
  • need to check GSON files
• Components and Changes
  • Frontend
  • Backend
• Tests / Data
• Dependencies
• Known Unknowns
• QA: local | testing | snapshot | other
• Development Estimate

In Code Review. Waiting for stripes-kint-components release. 

Currently not testable:

• Don't currently harvest through Title Only harvest
• Only triggered once daily. 
• Need to be able to trigger on snapshot. 

To test:

• Need to set up a Title KB
• Reset cursor, potentially via postman ... no endpoint (as doesn't go through okapi)

Otherwise - can test locally