ERM Sprint 147

Sprint Goal / Focus

Sprint Schedule

  • Sprint: 147
  • Release: 2022.3 Nolana  
    • Sprint 7 of 9 since Release Development Cycle Starts (Sprint 142) to Feature Freeze (Sprint 150)
    • Sprint 151: Module Release Deadline [FOLREL-549]
      • Backend 26 Oct 2022
      • Frontend 28 Oct2022
    • Sprint: Bugfix Release Deadline (2 Dec 2022) [FOLREL-550]

Development Meetings

Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

  • Monireh: all sprint
  • Owen: all sprint
  • Peter: 31 Aug, 1 Sep (Wolfcon)
  • Claudia
    • 22 Aug
    • 31 Aug, 1 Sep (Wolfcon)

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

  • Development Estimate

Sprint Focus

Maintenance

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2316 - Getting issue details... STATUS


ERM-2328 - Getting issue details... STATUS


ERM-2326 - Getting issue details... STATUS


ERM-2325 - Getting issue details... STATUS


ERM-2323 - Getting issue details... STATUS


ERM-2321 - Getting issue details... STATUS


ERM-2320 - Getting issue details... STATUS


ERM-2319 - Getting issue details... STATUS


ERM-2318 - Getting issue details... STATUS



UXPROD-3116 - Getting issue details... STATUS

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2314 - Getting issue details... STATUS

(question) Requires Elaboration
  • Approach

  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data

    • No tests to be written
  • Dependencies

    • Should amend the current behaviour to not create a new dashboard in the backend, so a user comes to a splash screen on first access
      • Ethan to stub an issue for Owen to review and prioritise after ERM-2314
      • Est: 0.5d to add a splash screen once 2314 is done
  • Known Unknowns

    • How will the order weight interact? Requires API.
  • QA: snapshot | local | testing | other

  • Development Estimate

No Feature

Issue ID

Sprint Backlog?

Notes / Estimates / Actions




Release Tasks (Nolana)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions





Brought In

Issue ID

Sprint Backlog?

Notes / Estimates / Action

ERM-2329 - Getting issue details... STATUS

(tick)

Developed externally.

PR Review by Bienenvolk.




Removed

Issue ID

Deferred to

Notes / Estimates / Actions







Planning Notes Template

  • Current State
  • TODO
  • Development Estimate

Rolled Over From Previous Sprint

Sprint Backlog

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


ERM-2304 - Getting issue details... STATUS
  • Approach

    • check that changes are already made for lifeycleStatus
  • Components and Changes

    • Frontend: none

    • Backend: mod

  • Tests / Data / Dependencies: NA

  • Known Unknowns: NA

  • QA: snapshot | local | testing | other

  • Development Estimate: Monday

UXPROD-3754 - Getting issue details... STATUS

ERM-2311 - Getting issue details... STATUS
  • Approach

    • add to package schema
    • add fields to ingest 
    • update adaptor
  • Components and Changes

    • Frontend: none

    • Backend: mod-agreements

  • Tests / Data: packageViewSpec.groovy 

    • add to existing JSON object
    • add new test for fields/filters (on Set) 
    • add new test for update
  • Dependencies: ERM-2288

  • Known Unknowns: 

  • QA: snapshot

  • Development Estimate: Monday

UXPROD-3754 - Getting issue details... STATUS

ERM-2306 - Getting issue details... STATUS

Add sibling list property to availabilityScope

  • Approach

    • create new entries as they are seen imported
    • store as refData (normalised objects, like packageContentType)
    • add refData to domain model
    • add refData to migrations
    • extend schema and ingest service
  • Components and Changes

    • Frontend: none

    • Backend: mod-agreements

  • Tests / Data: none, use package tests

  • Dependencies

    • required for 2307, 2308, 2309
  • Known Unknowns: none 

  • QA: snapshot

  • Development Estimate: 2d

UXPROD-3754 - Getting issue details... STATUS

ERM-2307 - Getting issue details... STATUS (question)
  • Approach

    • explicitly comment the behaviour /  business rule in the code
    • Add logic (if / elseif) inside adaptor
  • Components and Changes

    • Frontend: none

    • Backend: mod-agreements (adaptor)

  • Tests / Data: none

  • Dependencies: ERM-2306

  • Known Unknowns: none

  • QA: snapshot

  • Development Estimate: == ERM-2311

UXPROD-3754 - Getting issue details... STATUS

ERM-2308 - Getting issue details... STATUS

(question)
  • Approach

    • explicitly comment the behaviour /  business rule in the code
    • Add logic (if / elseif) inside adaptor
  • Components and Changes

    • Frontend: yes

    • Backend: none

  • Tests / Data: none

  • Dependencies:

    • ERM-2306

    • Gill to review frontend mockups based on ERM-2306 shape
  • Known Unknowns: none

  • QA: snapshot

  • Development Estimate: == ERM-2311

UXPROD-3754 - Getting issue details... STATUS

ERM-2309 - Getting issue details... STATUS

(question)
  • Approach

    • lookup the refdata
    • query refdata
    • filter on list
    • use selection rather than checkboxes doing lookup
    • publicationType is checkboxes - so, OR'd in filter, rather than AND
    • no default to be set 
    • no lookahead for now
  • Components and Changes

    • Frontend: ui-agreement

    • Backend: none

  • Tests / Data:

    • if we already have existing filter tests

  • Dependencies: ERM-2306

  • Known Unknowns

    • list size may encourage select rather than checkboxes
      • expecting to be in the order of 10s, rather than 100s
  • QA: snapshot 

  • Development Estimate: 1d

UXPROD-3754 - Getting issue details... STATUS

ERM-2310 - Getting issue details... STATUS

(question)
  • Approach

    • add new logic to packageIngestService lines 212-218
    • ensure save after block
    • use existing patterns for updating PTI
  • Components and Changes

    • Frontend: none

    • Backend: mod-agreements packageIngestService 

  • Tests / Data: package test data

  • Dependencies: no

  • Known Unknowns: none

  • QA: snapshot 

  • Development Estimate: small

UXPROD-3116 - Getting issue details... STATUS

ERM-2313 - Getting issue details... STATUS


  • Approach

  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data

  • Dependencies

  • Known Unknowns

    • Sorting: not expected for volumes of users expected in list (~10)
    • Is name handed from Users as a single name, or first/last name?
      • To be consistent across FOLIO, we should keep separate
    • Out of scope: giving user list access to non-manager users
    • Does Users pre-filter out inactive users?
  • QA: snapshot | local | testing | other

  • Development Estimate


ERM-2258 - Getting issue details... STATUS

(error)

Approach:

  • Can mock pluggable to check if plugin shows up
  • Check if card is displayed

Blocked

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions





In Development

Feature ID

Issue IDSprint Backlog?

Notes / Estimates / Actions

UXPROD-3754 - Getting issue details... STATUS

ERM-2288 - Getting issue details... STATUS

  • Current State
    • tested and working on gokb
    • had to set up frontend to test cursor
      • being hikari issue identified 
      • known hikari issue experienced which is not to be addressed
  • TODO
    • complete testing on on kbart
      • not sure how to test source updates, such as lifecycle
      • potentially not set initially from kbart
    • code cleanup and then PR
  • Development Estimate
    • Wed 10

UXPROD-3756 - Getting issue details... STATUS

ERM-2289 - Getting issue details... STATUS

  • Current State
    • Draft PR submitted, but not working
    • some routing changes needed
  • TODO
    • filters need re-writing
  • Development Estimate
    • ? 1d

ERM-2133 - Getting issue details... STATUS

In Code Review

UXPROD-3116 - Getting issue details... STATUS

ERM-2312 - Getting issue details... STATUS

  • Current State
    • code complete as far as issue is written
  • TODO
    • add weight order support, based on ERM-2314
  • Development Estimate: 0.5d
NA

ERM-2315 - Getting issue details... STATUS

  • Current State
    • No progress started
    • Previously rewritten to a single component
      • that may be covered for tests
  • TODO
    • extend getResourceIdentifier() with a returnAll boolean parameter (stripes-erm-components)
    • tweak test for getResourceIdenitifier
    • update ui-agreements to apply logic
    • add tests to eResourceIdentifier to check multiple cases
  • Development Estimate: <1d


For QA

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

ERM-1343 - Getting issue details... STATUS

ERM-2234 - Getting issue details... STATUS