ERM Sprint 145

Sprint Goal / Focus

Sprint Schedule

Development Meetings

Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

  • Claudia: sick w/c 25 Jul
  • Monireh: sick 1 Aug
  • Claudia: absent 3+ Aug

Lead Roles:

QA Environment: folio-snapshot

Present

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

UXPROD-3754 - Getting issue details... STATUS

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2288 - Getting issue details... STATUS

Peter Böhm 
  • Approach

    • all values should already be there, so no data changes
    • add a step when matching package to overwrite 
    • new service may be needed to keep it clean from ingest
    • need to do a deepCompare on big arrays ingested
    • same changes needed should be deep enough to work in all scenarios 
      • expect to develop on JSON or KBART
      • arrange for 
  • Components and Changes

    • Frontend: none

    • Backend:

      • new package enrichment function / service

      • change existing matching service / component
  • Tests / Data

    • no tests to create / update on ingest service
    • test data should already be in place
    • Owen to request Gokb access for Peter / Ethan
  • Dependencies: no

  • Known Unknowns: no

  • QA: snapshot 

  • Development Estimate: 1d (within sprint)

STRIPES-675 - Getting issue details... STATUS

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2150 - Getting issue details... STATUS



ERM-2152 - Getting issue details... STATUS



No Feature

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2289 - Getting issue details... STATUS

Uses existing API and existing UI pattern

  • Approach

    • Update filter navigation to support agreement lines option
      • Apply existing route
    • New SaS lookup
    • Set up new SaS page
      • not yet use the OA wrapper (hasn't gone through accessibility testing)
    • Tie the filter and results together using existing interface
    • Can use react-query from ground up
  • Components and Changes

    • Frontend: ui-agreements

    • Backend: none

  • Tests / Data

    • needs tests similar to AgreementRoute tests (ie, AgreementLinesRoute)
  • Dependencies: none

  • Known Unknowns

    • Gill to review removing button group, in favour of using top menu, as per other apps
  • QA: local | testing | snapshot | other

  • Development Estimate: 2d

ERM-2290 - Getting issue details... STATUS

Already search via specific fields via API

  • Approach
    • apply same UI consistent with agreements search widget
    • some wrangling to handle as array (not dropdown)
    • new pattern: spike subtask to test approaches inside or outside of SaS
  • Components and Changes

    • Frontend: ui-agreements

    • Backend: none

  • Tests / Data: no tests ... outcome of results is not tested

  • Dependencies / Known Unknowns: none

  • QA: snapshot 

  • Development Estimate: 3d

Release Tasks (Morning Glory Bug Fix)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2281 - Getting issue details... STATUS


ERM-2287 - Getting issue details... STATUS


ERM-2291 - Getting issue details... STATUS
ERM-2301 - Getting issue details... STATUS
ERM-2302 - Getting issue details... STATUS Ethan Freestone 


Brought In

Issue ID

Sprint Backlog?

Notes / Estimates / Action

ERM-2151 - Getting issue details... STATUS

ERM-2149 - Getting issue details... STATUS

ERM-2154 - Getting issue details... STATUS

ERM-2148 - Getting issue details... STATUS

Ethan Freestone Reopened for corrective work.

ERM-2283 - Getting issue details... STATUS

Minor adjustment. 

  • Development Estimate: <1h
ERM-2297 - Getting issue details... STATUS
ERM-2299 - Getting issue details... STATUS

ERM-2300 - Getting issue details... STATUS


ERM-2302 - Getting issue details... STATUS

ERM-2303 - Getting issue details... STATUS


Removed

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2249 - Getting issue details... STATUS

(error)
  • Not a small change
  • Needs more info from reporter to understand appropriate resolution
  • Re-assigned to reporter for clarification




Planning Notes Template

  • Current State
  • TODO
  • Development Estimate

Rolled Over From Previous Sprint

Sprint Backlog

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


ERM-2282 - Getting issue details... STATUS

  • Current State:
    • Fixed
  • TODO: 
    • Needs patch release of kint-components
    • need to then bump dependencies for both agreements (ERM-2281) and licenses (ERM-2291)
  • Development Estimate: 1h


ERM-2284 - Getting issue details... STATUS

  • Current State: verified
  • TODO: 
    • react-query clause migrated from stripes-connect needs fixing
    • PUT not DELETE
    • Owen to ADD testrails process for missing use case
  • Development Estimate: 1h

ERM-2285 - Getting issue details... STATUS

  • Current State
    • ERM-2286 done, but not sure that it will help
    • Not seeing issue anywhere but bugfest and mostly agreements linked through to eholdings
    • generic JDBC exception is seen in local logs (Ethan), but doesn't seem to be affecting functionality
      • probably not the same exception
  • Known Unknowns
    • network connection issue not being handled by grails and bubbles up as a state exception 
    • not sure whether there is a change in
      • eholdings api
      • bugfest environment setup
    • something to do with
      • multi-tenancy, and starving of database connections?
      • how okapi status values are used?
      • agreement lines not displaying?
  • TODO
    • JDBC exceptions need to be handled separately - more triage needed (Ethan)
    • What has changed between releases? (Owen)
    • Can this be reproduced on snapshot (7.1.4 v 7.2.0)? (Owen)
    • Can we get eHolding logs? (Owen)
    • BF-315 Has parameter passing changed in bugfest environment? (Ian)
  • Development Estimate: UNKNOWN

In Development

Feature ID

Issue IDSprint Backlog?

Notes / Estimates / Actions

FAT-82 - Getting issue details... STATUS

ERM-2252 - Getting issue details... STATUS

  • Current State
  • TODO: finish test
  • Development Estimate: Wed

FAT-82 - Getting issue details... STATUS

ERM-2257 - Getting issue details... STATUS

  • Current State: nearly done 
  • TODO: 2 more tests left
  • Development Estimate: Mon pm 

FAT-82 - Getting issue details... STATUS

ERM-2255 - Getting issue details... STATUS

Pending Code Review

FAT-82 - Getting issue details... STATUS

ERM-2256 - Getting issue details... STATUS

Pending Code Review


For QA

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


ERM-946 - Getting issue details...