Sprint Goal / Focus 

  • NA

Sprint Schedule

  • Sprint: 170
  • Release: 2023.2 Poppy  
    • Sprint 15 of 17 since Release Development Cycle Starts (Sprint 159) to Feature Freeze (Sprint 175: 6 Oct 2023)
    • Sprint 176: Module Release Deadline (13 Oct 2023) [FOLREL-565]
    • Sprint 178: Bugfix Release Deadline (10 Nov 2023) [FOLREL-581]

Development Meetings

  • Wed 30 Aug
  • Mon 4 Sep
  • Wed 8 Sep

Sprint Capacity

Team Availability: Schedule | Calendar

Notes / Exceptions:

  • Monireh: back Mon 4 Sep

Lead Roles:

QA Environment: 

  • folio-snapshot, folio-snapshot-2

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

  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 

(warning) - not ready

(question) - pending triage / planning


Sprint Focus


Planning Notes Template

  • Triage

  • Approach

  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target: 

  • Development Estimate


UXPROD-4436 - Getting issue details... STATUS

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-3010 - Getting issue details... STATUS

Jack Golding 

  • Triage

  • Approach
    • Use has  and has not  instead of 1 or 0, etc
    • use default logic of AND taking precedence over OR
    • preserve filter state in url
      • AND/OR filter options cannot be added until validated
    • no ux for non-valid filters in ERM
      • Use apply button to trigger validation only if needed. 
      • Clear invalid filters 
    • May need arrayMutators in a form for field arrays

  • Components and Changes

    • Frontend: ui-agreements, may need changes to SKC

    • Backend: NA

  • Tests / Data / Dependencies

    • add unit test on new filter component
    • interactors for future integration tests

  • Known Unknowns:

    • final-form or form: if ff, will need state arrays

  • QA: snapshot 

  • Release Target: Poppy

  • Development Estimate

No Feature

Issue ID

Sprint Backlog?

Notes / Estimates / Actions


ERM-3014 - Getting issue details... STATUS 		Claudia Malzer 

  • Approach

    • parallel batch fetch users (and user names), using component from stripes-erm-component
    • pagination is complicated for users as user fetching is an upfront check for permission verification - fetch 100 at a time, without max limit (ie, use default of infinity)

  • Components and Changes

    • Frontend: ui-dashboard

    • Backend: none

  • Tests / Data / Dependencies: NA

  • Known Unknowns: NA

  • QA: snapshot 

  • Release Target: Poppy

  • Development Estimate: 


ERM-3018 - Getting issue details... STATUS 		(question)

This would enable pushKb testing against Gokb data sources, independent of FOLIO release cycles

  • Triage

    • migration - what to do with existing titles
    • ingest from multiple sources: preventing title duplication
    • currently don't save gokb uuid
    • would be three cycles before using id 
    • class 1 namespaces are not checked in any breaking/switching order, so title would have to be promoted as first match check (though that would remove then re-add titles) 

More discussion needed to thrash out consequences.

ERM-3012 - Getting issue details... STATUS


(question) 

May not be technically feasible. Needs investigation to determine approach. 

  • relationshipTypes will need to become frontend translations
  • Cannot currently be omitted/suppressed from picklist dropdowns (as this is dynamically generated)
  • Not expecting these to be user editable
  • In the future (so out of scope now), instead of using as refdata, should use domain class that uses refdata for the relationship types. 


ERM-3013 - Getting issue details... STATUS 		Claudia Malzer 
ERM-3017 - Getting issue details... STATUS



DRAFT

SI-34 - Getting issue details... STATUS


DRAFT

Tests

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

NA




Release Tasks (Flower Release / CSP)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

NA



Release Tasks (Non-Flower Release)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

NA



Maintenance

Issue ID

Sprint Backlog?

Notes / Estimates / Actions







Changes

(plus) Added

(minus) Removed: note whether rescheduled or deferred

Feature ID

Issue ID

Change

Notes





Rolled Over From Previous Sprint


Planning Notes Template

  • Current State
  • TODO
  • Development Estimate

In Development

Feature ID

Issue IDSprint Backlog?

Notes / Estimates / Actions


ERM-2841 - Getting issue details... STATUS

Ethan Freestone 

For Code Review

UXPROD-3890 - Getting issue details... STATUS

ERM-2992 - Getting issue details... STATUS

Ethan Freestone  

For Code Review

ERM-3016 - Getting issue details... STATUS

Ethan Freestone 

Will merge with ERM-2937


Sprint Backlog

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions





Blocked

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


ERM-2937 - Getting issue details... STATUS

(minus)

Blocked by STSMACOM-775 - Getting issue details... STATUS

Will need some limited regression testing if stripes components changes are merged


In QA


Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


ERM-2989 - Getting issue details... STATUS

ERM-2994 - Getting issue details... STATUS

ERM-2995 - Getting issue details... STATUS

ERM-2988 - Getting issue details... STATUS

ERM-2990 - Getting issue details... STATUS

ERM-2987 - Getting issue details... STATUS

ERM-2991 - Getting issue details... STATUS

ERM-2984 - Getting issue details... STATUS

ERM-2985 - Getting issue details... STATUS

ERM-2986 - Getting issue details... STATUS

ERM-2996 - Getting issue details... STATUS

ERM-2997 - Getting issue details... STATUS

ERM-2998 - Getting issue details... STATUS




ERM-2641 - Getting issue details... STATUS




ERM-2934 - Getting issue details... STATUS




ERM-2922 - Getting issue details... STATUS




ERM-1795 - Getting issue details... STATUS




ERM-2189 - Getting issue details... STATUS




ERM-2630 - Getting issue details... STATUS


Initial testing worked so far - successfully pushed package info.

TODO: Add test plan info to issue (started)


ERM-2815 - Getting issue details... STATUS




ERM-2966 - Getting issue details... STATUS




ERM-2967 - Getting issue details... STATUS


ERM-2973 - Getting issue details... STATUS




ERM-2979 - Getting issue details... STATUS




ERM-2980 - Getting issue details... STATUS




ERM-2993 - Getting issue details... STATUS




For Elaboration

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions






For Release Prep / Pending Testrails

Cross-check against e2e Jira issues

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


ERM-2421 - Getting issue details... STATUS




ERM-1110 - Getting issue details... STATUS




ERM-2628 - Getting issue details... STATUS


ERM-2923 - Getting issue details... STATUS




SI-24 - Getting issue details... STATUS




Bugfix Cycle

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions







Sprint Summary

ERM

Key Summary T Assignee Status Component/s
Refresh


Dashboard

Key Summary T Assignee Status Component/s
Refresh

Other

Key Summary T Assignee Status Component/s Labels
Refresh

No Label

Key Summary T Assignee Status Component/s
Refresh