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.

Meeting Details

Date

 

Time

9:05am ET, 2:05pm UK, 3:05pm Germany

Location

Video Call in

Previously2022-03-23 ERM Weekly Delivery Update
ReferencesJIRA Issue Board

Goals

Participants

Apologies

Discussion items

Time

Item

Notes

<5 minsIntroductions

Call Priorities

WIP 

  • What progress or impediment on previously stated actions?
  • What's left to do?
  • Any new unknowns?
  • What help or input is needed?
  • When expected to be ready for review?

In Progress

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1986
    /
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1989
    Progress / Impediments: NA
    • TODO
      • Refactoring, eg, variable names
      • Styling
      • Tests
    • New unknowns: NA
    • Help or input needed: NA
    • ETA for review: COP Wednesday: set up call between Monireh and Ethan
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2045
    • Progress / Impediments
      • Migrations done and working
      • GET on 2/3 Many fields not expanding (NULL showing)
      • PUT is behaving as expected
    • TODO:
      • Test via Curl 
      • Add value for lifecycleStatus
      • Add array for packagDescriptionUrls
      • Remove blocks
      • Switch altResourceNames to expand on eresourceAdd for new view for domain class
    • New unknowns: NA
    • Help or input needed: None
    • ETA for review: Thu 22 am Mon 28 pm Wed 30 pm
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2044
    /
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-778
     
    • Progress / Impediments
      • all code written in stripes-kint-components
      • requires ERM-2058
    • TODO: 
      • Claudia to complete erm-2068, erm-1066 to resolve 2044 and 778
    • New unknowns
    • Help or input needed
    • ETA for review: Sprint 137
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1850
    • Progress / Impediments
      • three viable approaches identified and tested at small scale
      • waiting for full ingest 
      • postman tooling written for performance testing
    • TODO: 
      • run query for each three TI fetch methods
      • assess performance across methods
    • New unknowns
    • Help or input needed
    • ETA for review
      • need to complete full ingest today to avoid having to dump db for reshare 

Pending

Blocked

  • Are the blocking conditions still relevant? 
  • What action is needed to unblock, and by whom?

Needs Elaboration

  • Who needs to be involved in the elaboration process? 
  • What is the timeframe for getting input?
  • When is the issue expected to be ready for development?

Sprint Backlog

  • Who is picking up what next?
  • When is next issue expected to start / complete?
  • Anything needed to start next issue (dependencies or clarifications)?

Blocked

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

    • Blocking conditions
    • Action needed
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2062

    • Blocking conditions
    • Action needed

Needs Elaboration

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2046
    • Who / When:
      • to discuss with Martina on 30 Mar
    • ETA Ready for Dev: 
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2059
    • Who / When: NAPeter
    • ETA Ready for Dev: Sprint 137136

Sprint Backlog - Next Up

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2048
    • done, ready for QA
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2068
  • Claudia: 
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-1313
    • Pair on licenses for ERM-2048, ERM-778, ERM-2044
  • Ethan:
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-1850
      ?
    • NA
  • Monireh: NAMonireh: 
  • Peter:  
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-2059
      • OAI to package schema to package ingest
      • will need adding to package schema
      • then grab from pacjage package ingest
      • package description urls and description not currently available - proceed without




At Risk

  • What is now at risk of not being started this sprint?
  • Do any of these take priority over other sprint backlog items?

Sprint Backlog - to follow

  • RTL

Sprint Backlog -  At Risk

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2048
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2068

In Review

  • Any impediments to review or QA?
  • Any useful context, implementation choices or limitations for the reviewer/tester to know ?


Code Review: 

  • NA

QA / UAT 

  • Aim for Monday for Lotus Bugfix
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-2051
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-2063
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-2065
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-778
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-2016
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-2017
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-2018

Bugfix Cycle 

  • NA



Release Candidates

  • What has passed QA since last dev call?
  • What has been closed since last dev call?

Accepted

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1979
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2043

Closed: Lotus Hotfix 1

  • NA

Closed: Morning Glory R2022.2

Features

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

RTL / Other Tests

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1319
<10 mins

AOB


New Issues

Added to sprint

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2062
    • In Triage - not seen on snapshot
    • blocked by ERM-2067
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2066
    • fix in stripes-connect is disproportionate to refactor with react query
    • to be reviewed after others
    • would want to replace separately for agreement (line)s initially to make sure it worked
      • requires untangling from existing setup
    • maybe half a sprint to do properly
    • medium priority for Morning Glory
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2067
    • highest priority of incoming bugs
    • blocked by STCOM-931
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2063
    • Needs some triage
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2065

Not added to sprint

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

Other

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1958
    • changes made to PR
    • pending acceptance by Orgs team