ERM Sprint 150

Sprint Goal / Focus

  • Feature Freeze

Sprint Schedule

  • Sprint: 150
  • Release: 2022.3 Nolana  
    • Sprint 9 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:

  • Peter: A/L available 5, 4, 12-13 Oct
  • Claudia: Absent all sprint
  • Ethan: AL 6-12 Oct

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 

(warning) - not ready

(question) - pending triage / planning


Planning Notes Template

  • Triage

  • Approach
  • Components and Changes

    • Frontend

    • Backend

  • Tests / Data

  • Dependencies

  • Known Unknowns

  • QA: snapshot | local | testing | other

  • Development Estimate

Sprint Focus

UXPROD-3754 - Getting issue details... STATUS

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2370 - Getting issue details... STATUS

  • Approach

    • review how abstractive enrichment calls work
    • unhook/disconnect gokb specific workflow from enrichment (rather than remove)
      • check boolean for requiresSecondaryEnrichmentCall
      • should be able to just make this false
    • change main body of adaptor to add new fields into schema
  • Components and Changes

    • Frontend: none

    • Backend: gokbOAI adaptor inside mod-agreements

  • Tests / Data: no stream tests

  • Dependencies / Known Unknowns: none

  • QA: snapshot 

    • add some seed data to test
    • also to note performance boost/hit
  • Development Estimate: 2d

UXPROD-3756 - Getting issue details... STATUS

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2356 - Getting issue details... STATUS

  • Approach

    • Store local state to see whether checked or not
    • On Save and Close check state and route accordingly
    • Add this option to the footer to use in New and Edit form
    • May have to change shape of submit handler to transport the state to next stage
  • Components and Changes

    • Frontend: ui-agreements

    • Backend: none

  • Tests / Data: appearance of checkbox

  • Dependencies / Known Unknowns: No

  • QA: snapshot 

  • Development Estimate: 2d

ERM-2368 - Getting issue details... STATUS

(tick) 
  • Approach

    • use existing pattern to convert string to url
    • optionally include PO line links
  • Components and Changes

    • Frontend: ui-agreements, ViewComponent, FIlterComponent

    • Backend: none

  • Tests / Data: No

  • Dependencies / Known Unknowns: No

  • QA: snapshot

  • Development Estimate: <0.5d

ERM-2343 - Getting issue details... STATUS

  • Approach

    • issue/concern that stripes handles null selection
    • Remove manually set default - should just work then 
    • Check that when making call, it sets nothing as same as qindex when all set
  • Components and Changes
    • Frontend: ui-agreements

    • Backend: none

  • Tests / Data: No

  • Dependencies:

    • may be affected by Stripes changes to enable ERM-2342 in STSMACOM-700
  • Known Unknowns

    • expecting to be problematic with complications around filter resets
  • QA: snapshot

  • Development Estimate: <0.25d if no stripes related fallout

No Feature

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2362 - Getting issue details... STATUS

(tick)


  • Triage

    • category and context are different fields
    • context is just never sent in payload when removing
  • Approach

    • always send down a blank string instead of nothing/null
  • Components and Changes

    • Frontend: stripes-kint-components

    • Backend: none

  • Tests / Data: No

  • Dependencies: 

    • duplicated by ERM-2364
  • Known Unknowns: none

  • QA: snapshot | bugfest

  • Development Estimate: 0.5d

ERM-2364 - Getting issue details... STATUS

(error)
  • Triage: duplicate of ERM-2362

ERM-2359 - Getting issue details... STATUS

(tick)


In QA - should be resolved as a result of fix in web-toolkit and stripes-kint-component

ERM-2360 - Getting issue details... STATUS

(tick)


In QA - should be resolved as a result of fix in web-toolkit and stripes-kint-component

ERM-2366 - Getting issue details... STATUS

(tick)


  • Triage

    • doesn't appear to be a regression - confirmed on Lotus
  • Approach

    • We already split out what we're handling as core and supplementary
    • Key on that to choose whether to display blank 
    • Add displayCategory prop to SEC/documentCard
      • default to true
      • set to false in coreDocs (ui-licenses)
  • Components and Changes

    • Frontend: stripes-erm-components, ui-licenses

    • Backend: none

  • Tests / Data: extend SEC/documentCard test for non-empty scenario

  • Dependencies / Known Unknowns: none

  • QA: snapshot 

  • Development Estimate: 0.5d

ERM-2190 - Getting issue details... STATUS

(error)
  • Triage

    • toaster is not handled uniquely by ERM 
    • OS to take back to reporter
  • Formatted message in toaster is handled by React but not processed by stripes in an accessible way

ERM-2371 - Getting issue details... STATUS

(tick)


  • Triage

    • done in agreements
    • cannot be backported to Morning Glory
    • previously fixed in 2217
  • Approach: see line changes
  • Components and Changes

    • Frontend: ui-licenses, ui-agreements

    • Backend: none

  • Tests / Data

  • Dependencies / Known Unknowns: none

  • QA: snapshot 

  • Development Estimate: <0.5d

ERM-2350 - Getting issue details... STATUS

(tick)
  • Approach

    • Replace empty div with name of component
  • Components and Changes

    • Frontend: ui=dashnb

    • Backend

  • Tests / Data: ?

  • Dependencies / Known Unknowns: none

  • QA: snapshot | local | testing | other

  • Development Estimate: <0.5d

Release Tasks (Nolana)

Issue ID

Sprint Backlog?

Notes / Estimates / Actions




Maintenance

Issue ID

Sprint Backlog?

Notes / Estimates / Actions

ERM-2331 - Getting issue details... STATUS

Defer to end of sprint

Changes

(plus) Added

(minus) Removed: note whether rescheduled or deferred

Feature ID

Issue ID

Change

Notes


ERM-2373 - Getting issue details... STATUS

(plus)

ERM-2374 - Getting issue details... STATUS

(plus)

ERM-2375 - Getting issue details... STATUS

(plus)

ERM-2376 - Getting issue details... STATUS

(plus)

ERM-2379 - Getting issue details... STATUS

(plus)

ERM-2380 - Getting issue details... STATUS

(plus)

ERM-2377 - Getting issue details... STATUS

(plus)

ERM-2379 - Getting issue details... STATUS

(plus)

ERM-2380 - Getting issue details... STATUS

(plus)

ERM-2381 - Getting issue details... STATUS

(plus)

ERM-2383 - Getting issue details... STATUS

(plus)

ERM-2385 - Getting issue details... STATUS

(plus) 



ERM-2190 - Getting issue details... STATUS

(minus)Cannot reproduce. Removed by reporter.

ERM-2261 - Getting issue details... STATUS

(plus)

ERM-2262 - Getting issue details... STATUS

(plus)

ERM-2386 - Getting issue details... STATUS

(plus)




Planning Notes Template

  • Current State
  • TODO
  • Development Estimate