Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Sprint Goal / Focus 

  • Poppy Feature Freeze

Sprint Schedule

  • Sprint: 167
  • Release: 2023.2 Poppy  
    • Sprint 9 of 9 since Release Development Cycle Starts (Sprint 159) to Feature Freeze (Sprint 167)
    • Sprint 168: Module Release Deadline (30 Jun 2023) [FOLREL-565]
    • Sprint 171: Bugfix Release Deadline (4 Aug 2023) [FOLREL-581]

Development Meetings

  • Wed 7 Jun
  • Mon 12 Jun
  • Wed 14 Jun

Sprint Capacity

Team AvailabilitySchedule | Calendar

Notes / Exceptions:

  • NA

Lead Roles:

QA Environment: 

  • folio-snapshot, folio-snapshot-2

Present


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

Table of Contents

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

(warning) - not ready

(question) - pending triage / planning


Sprint Focus


Info
iconfalse
titlePlanning Notes Template
  • Triage

  • Approach
  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target: 
  • Development Estimate


Jira Legacy
serverSystem

Jira

JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-4333

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-2934

  • Triage

  • Approach
    • Add JSON file
    • Review ERM-1651 for example from Agreements
    • Review mod-service-interaction to see how that consumes the file
  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Release Target: 
  • Development Estimate

FEATURE

Issue ID

Sprint Backlog?

Notes / Estimates / Actions


Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-2630

  • Current State
    • ERM-2916 mostly done
  • TODO
    • ERM-2916 final 
    • ERM-2917 not started
    • Look at title push
  • Development Estimate: expected today

No Feature

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-2935


  • Triage

    • React thinks the import is an object not a function
    • Fix is available, but
      • changes the pattern used everywhere
      • doesn't inform the cause, so we don't have any better understanding of what the issue really is
  • Approach
    • further diagnosis by individually pinning dependencies
    • start with non-folio deps
  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data / Dependencies

  • Known Unknowns: all of it

  • QA: snapshot 

  • Release Target: Poppy
  • Development Estimate: ?

Tests

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

NA




Release Tasks (Nolana 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

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-2911


  • Current State
    • Number Generator feature pending
  • TODO
    • Release SKC after NumGen changes made
  • Development Estimate: Minimal- This sprint

Changes

(plus) Added

(minus) Removed: note whether rescheduled or deferred

Feature ID

Issue ID

Change

Notes

Jira Legacy
serverSystem JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-4340

Jira Legacy
serverSystem JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-2937
 

  • Approach

    • change on route multiple to single fetch
    • get value of offset to drive which page to get
    • check impacts of
      • updates for next/prev
      • focus shift 
    • new pattern that can be applied to other related issues
    • no change to limit setting (ie, via constant)
  • Components and Changes

    • Frontend: ui-agreements

    • Backend: none

  • Tests / Data / Dependencies: NA

  • Known Unknowns: NA

  • QA: snapshot 

  • Release Target: Poppy
  • Development Estimate: 


Jira Legacy
serverSystem JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keySI-23



Rolled Over From Previous Sprint


Info
titlePlanning Notes Template
  • Current State
  • TODO
  • Development Estimate

In Development

Feature ID

Issue IDSprint Backlog?

Notes / Estimates / Actions


Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-2641

  • Current State
    • migrations are not accessible in a production docker build
  • TODO
    • Steve to look into why the jar isn't building
  • Development Estimate
    • ?? 

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-4271

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-2923

  • Current State
    • frontend part is done
    • input from Steve re bubbling up changes in hierarchy
    • Removed from scope: changes to identifier or coverage
  • TODO
    • handle database change by listening for identifier change at tip of domain classes (eg, TI, PTI etc), and bubble up changes to parent in hierarchy
    • Add event listener for when a TI identifier is updated or created, the parent object should grab that last updated of the identifier and trigger a save of the parent object 
  • Development Estimate
    • ?


Sprint Backlog

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

Jira Legacy
serverSystem

Jira

JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-3890


Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-2421

  • Current State
    • Dev complete. PR reviewed. Design change requested.
  • TODO
    • Move agreement POST to the modal instead of basket route, as the basket shouldn't logically handle that for an agreement.
    • Move agreement PUT to form level
  • Development Estimate
    • end of day

Blocked

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

NA




In QA

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

NA

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-2790

Questions arising from QA/review


For Elaboration

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

NA






For Release Prep / Pending Testrails

Cross-check against e2e Jira issues

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

NA

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-2929

(tick)Waiting for deployment to Nolana





Bugfix Cycle

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions

NA







Sprint Summary

ERM

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,assignee,status,components
columnskey,summary,type,assignee,status,components
maximumIssues20
jqlQuerylabels != release and labels in (licenses, agreements, erm) and Sprint = 1681 and issuetype in standardIssueTypes()
serverId01505d01-b853-3c2e-90f1-ee9b165564fc


Dashboard

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,assignee,status,components
columnskey,summary,type,assignee,status,components
maximumIssues20
jqlQuerylabels = dashboard and Sprint = 1681
serverId01505d01-b853-3c2e-90f1-ee9b165564fc

Other

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,assignee,status,components,labels
columnskey,summary,type,assignee,status,components,labels
maximumIssues20
jqlQuery(labels = release or labels not in (licenses, agreements, erm, dashboard)) and Sprint = 1681
serverId01505d01-b853-3c2e-90f1-ee9b165564fc

No Label

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,assignee,status,components
columnskey,summary,type,assignee,status,components
maximumIssues20
jqlQuerylabels is empty and Sprint = 1681
serverId01505d01-b853-3c2e-90f1-ee9b165564fc