Sprint Goal / Focus 

  • NA

Sprint Schedule

  • Sprint: 174
  • Release: 2023.2 Poppy  
    • Sprint 16 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 13 Sep
  • Mon 18 Sep
  • Wed 20 Sep

Sprint Capacity

Team Availability: Schedule | Calendar

Notes / Exceptions:

  • Jack: Mon 11 

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

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2893 - Getting issue details... STATUS

Claudia Malzer 

  • Triage

  • Approach
    • Build up the filter UI
    • Open modal with filter wrangling 
    • Pair with Jack on ERM-3010 to ensure consistency
    • Save modal with transformed shape

  • Components and Changes

    • Frontend: stripes-erm-components

    • Backend: NA

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target: 

  • Development Estimate

No Feature

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-3017 - Getting issue details... STATUS


Ian Ibbotson 

DRAFT

ERM-3024 - Getting issue details... STATUS

Claudia Malzer 

  • Triage

    • issue is presenting because of way we are pushing react/ff 
  • Approach
    • short term:
      • make button click async
      • await change call
      • remove linting error
    • longer-term (out of scope): ERM-1909

  • Components and Changes

    • Frontend: ui-agreements

    • Backend: NA

  • Tests / Data / Dependencies: may need test fix if fails

  • Known Unknowns: NA

  • QA: snapshot 

  • Release Target: Poppy 

  • Development Estimate

Tests

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2836 - Getting issue details... STATUS

Monireh Rasouli 

  • Approach

    • incorporate into existing agreement line lifecycle test to reduce test run overhead
    • setup and test administration is done via API
    • test execution is done via UI

  • Components and Changes: 

    • Frontend: stripes-erm-testing

    • Backend: NA

  • Tests / Data / Dependencies: Extends ERM-2841

  • Known Unknowns: NA

  • QA: snapshot 

  • Release Target: Poppy

ERM-2840 - Getting issue details... STATUS

(error)

  • Triage

  • Approach
    • will need to establish new config/patterns for file/download handling
    • needs investigation work

  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data / Dependencies

  • Known Unknowns

    • where, how and whether to download a file with cypress
      • can test for presence of file
      • but don't necessarily want to download the file for 
    • separately test JSON contents (through the console)

ERM-2813 - Getting issue details... STATUS




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

Jack Golding 



ERM-3018 - Getting issue details... STATUS

Ethan Freestone 

  • Current State
    • Process defined
    • Core code in place (except sibling scenarios)
  • TODO
    • Handle sibling wrangling scenarios
    • Dev test additional scenarios
    • Upgrade testing, ie, QA vs existing data or vs existing resolver service, will have to be done alongside dev testing because of backend resource requirements
  • Development Estimate


ERM-2934 - Getting issue details... STATUS


In Code Review

ERM-2841 - Getting issue details... STATUS


In Code Review

ERM-2992 - Getting issue details... STATUS


In Code Review

ERM-3014 - Getting issue details... STATUS


In Code Review

ERM-3013 - Getting issue details... STATUS


In Code Review

ERM-3012 - Getting issue details... STATUS


In Code Review

ERM-3019 - Getting issue details... STATUS


In Code Review


Sprint Backlog

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


ERM-3020 - Getting issue details... STATUS




ERM-3022 - Getting issue details... STATUS



Blocked

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


ERM-3016 - Getting issue details... STATUS


Also relates to ERM-2960 - Getting issue details... STATUS ? 


ERM-2937 - Getting issue details... STATUS



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




ERM-1795 - Getting issue details... STATUS




ERM-2189 - Getting issue details... STATUS




ERM-2630 - Getting issue details... STATUS




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-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




ERM-1795 - Getting issue details... STATUS




ERM-2979 - Getting issue details... STATUS




ERM-2993 - 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