Versions Compared

Old Version 3

changes.mady.by.user Jag Goraya

Saved on

compared with

New Version Current

changes.mady.by.user Jag Goraya

Saved on

Key

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

Sprint Goal / Focus 

  • NA

Sprint Schedule

  • Sprint: 170
  • Release: 2023.2 Poppy  
    • Sprint 13 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 2 Aug
  • Mon 7 Aug
  • Wed 9 Aug

Sprint Capacity

Team Availability: Schedule | Calendar

Notes / Exceptions:

  • Owen: off 31 Jul - 4 Aug

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


FEATURE

Issue ID

Sprint Backlog?

Notes / Estimates / Actions




Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-3890

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2992

Jack Golding 

  • Triage

  • Approach
    • public lookup will need a postman or curl 
    • check integration tests

  • Components and Changes

    • Frontend: NA (if frontend doesn't break)

    • Backend: mod-agreements

  • Tests / Data / Dependencies

  • Known Unknowns

  • QA: snapshot 

  • Release Target: Poppy

  • Development Estimate: 

No Feature

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2980

Claudia Malzer 

  • Triage

  • Approach
    • uses TokenPickers/TokenDatePicker component
    • changeOutputValue sets the single text field on form
      • console.log form values and states 
    • either state is not reset or form value is not changing
    • When changing the widget between field types, the date clears
      • this should also

  • Components and Changes

    • Frontend: TokenPickers/TokenDatePicker component

  • Tests / Data / Dependencies: NA

  • Known Unknowns: NA

  • QA: snapshot 

  • Release Target: Poppy 

  • Development Estimate: 

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2982

(error) 

Closed in favour of ERM-2992

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
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2988

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2989

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2990

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2987

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2991

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2984

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2985

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2986

SET, SKC, SEC  - Ethan Freestone  

Others - Claudia Malzer 

Need for stripes-erm-testing and stripes-kint-components also? 

  • For stripes-kint-components 
    • Currently straddles stripes 7.x and 8.x and react 17 
    • Could include with not instead of, as SKC is used by other projects
    • Or 
    • Other non-ERM modules affected:
      • OA: new release with multiple changes expected
      • Serials: no expected releases
      • Reshare: no 
      • NumGen: releases with Poppy
  • ui-dashboard
  • ui-stripes-registry
  • stripes-erm-handler
  • platform-erm
    • bump major version
    • change react dependencies


Implementation

  • use ^ not ~ dependency for our components
  • make changes to modules individually outside of a workspace, and run tests
  • merge all when all passed
  • Order: 
    • In shared workspace
      • stripes-erm-testing > cypress tests
        • may need changes to accommodate moved or changed functions
      • stripes-kint-components
        • will need to bump version in dependent modules
      • stripes-erm-components
    • platform-erm
      • bump major version (if ^ dependency)
      • bump stripes and stripes-cli 
      • change react dependencies (via yarn)
    • Then
      • other modules individually or cleanly (after resting workspace) to previous workspace
      • bump each module to next major version





Changes

(plus) Added

(minus) Removed: note whether rescheduled or deferred

Feature ID

Issue ID

Change

Notes


Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2979

Claudia Malzer 



Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2993

Claudia Malzer 

  • Approach

    • Follow pattern for existing amendments view
    • New viewRoutes needed to remember where the view is reached from (as with packages)
    • use same id for search & filter pane to avoid resizing issue (as with packages)

  • Components and Changes

    • Frontend: ui-licenses

    • Backend: NA

  • Tests / Data / Dependencies: NA

  • Known Unknowns: 

    • filters to be defined

  • QA: snapshot 

  • Release Target: Poppy

  • Development Estimate: 1w


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
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2815

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2841


In Code Review


Sprint Backlog

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2972


  • Current State
    • Needs to fall back to spike for more technical investigation
  • TODO
  • Development Estimate

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2934


  • Current State
  • TODO
    • Add safety to prevent error when rendering 
  • Development Estimate

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2966


  • Current State
    • No release provided for web-toolkit
    • Steve away now for 2 weeks
  • TODO
    • Add safety to prevent error when rendering 
  • Development Estimate

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2969



Blocked

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions


Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-2922


  • Current State
    • Pending merge of PR
  • TODO
    • Merge PR
    • Revisit branch that uses stripes components
    • Push to QA
  • Development Estimate: trivial

In QA

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions






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










Bugfix Cycle

Feature IDIssue IDSprint Backlog?

Notes / Estimates / Actions







Sprint Summary

ERM

Jira
serverFOLIO Issue Tracker
columnIdsissuekey,summary,issuetype,assignee,status,components
columnskey,summary,type,assignee,status,components
maximumIssues20
jqlQuerylabels != release and labels in (licenses, agreements, erm) and Sprint = 1684 and issuetype in standardIssueTypes()
serverId6ccf3fe4-3301-368a-983e-20c466b11a49


Dashboard

Jira
serverFOLIO Issue Tracker
columnIdsissuekey,summary,issuetype,assignee,status,components
columnskey,summary,type,assignee,status,components
maximumIssues20
jqlQuerylabels = dashboard and Sprint = 1684
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

Other

Jira
serverFOLIO Issue Tracker
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 = 1684
serverId6ccf3fe4-3301-368a-983e-20c466b11a49

No Label

Jira
serverFOLIO Issue Tracker
columnIdsissuekey,summary,issuetype,assignee,status,components
columnskey,summary,type,assignee,status,components
maximumIssues20
jqlQuerylabels is empty and Sprint = 1684
serverId6ccf3fe4-3301-368a-983e-20c466b11a49