ERM Delivery
Space shortcuts
Child pages
  • 2021-10-06 ERM Weekly Delivery Update

Versions Compared

Old Version 1

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:15am ET, 2:15pm UK, 3:15pm Germany

Location

Video Call in

Previously2021-09-29 ERM Weekly Delivery Update
ReferencesJIRA Issue Board

Goals

Participants

Apologies

NA

Discussion items

Time

Item

Notes

<5 minsIntroductions

Previous Actions

NA


In Review

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


Code Review: 

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1259
    /
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1258
    • 1259: component needed to be rendered in a field
    • 1258:
      • coverage is low. issues with testing.
      • Monireh to clarify and confer with Adi
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1887
    • passed to QA
    • TODO: check for further regressions - comparing with Juniper (last known working release) 
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1704
    • passed review - pending merge
    • TODO: Ethan to make merge request of Zak or John Malco

QA / UAT 

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1628
    • original issue no longer there
    • however, German translation cannot be checked until Localize updates translations 
      • currently appears (falls back?) in English on snapshot
      • may get better info on testing environment
    • TODO: request Localize refresh from Peter Murray
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1700
    • Q: should changes be reflected in dashboard? A: not currently
    • there is an issue with showing phone/email in Dashboard, which suggests the behaviour needs to be overwritten
      • there is a separate card in Dashboard that overwrites the stripes-erm-components view
      • this difference is accepted 
    • good to proceed to For Release,
    • TODO: testrails review by Owen
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1798
    • returned to dev
    • changing integration tests has resulted in minor tweaks that will require testing
      • these have passed now, which satisfies remaining code review requirements
    • TODO: 
      • push to QA
      • rerun QA
      • test with switch for idFirst and titleFirst matching

Bugfix Cycle 

  • NA



WIP 

  • What progress or impediment on previously stated actions?
  • What's left to do?
  • 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-1813
    • can confirm getRelatedTitles does get give the expected resultstest with PT, PTI and TI
    • showing up as expected in json export
    • comparing with endpoints, looking favourable at the moment
    • TODO:
      • review against given scenarios
      • setup integration tests for export 
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1852
    • changes made in ui-dashboard and stripes-components
    • TODO: 
      • raise PR for JC and Adi review with ERM reference
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1287
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1661

Pending

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

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?

Blocked

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

Sprint Backlog - Next Up

  • Claudia: 
    • PackageCardExternal:
      • pointers at existing card tests
      • nothing special 
      • mostly just key values
  • Peter:  Incorporate ERM-1879 into ERM-1813
  • Ethan:  review Sprint 125 options
  • Adi: 
    • frontend releases
  • Monireh:  RTL

Sprint Backlog - to follow

  • NA

Needs Elaboration

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

Blocked

  • NA

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 

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1287
    • at risk this sprint because of extra time needed for new sas related RTL tests for ERM-1661 
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1733
    • pending reproduction in hosted environment

Release Candidates

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

Accepted 

  • NA

Closed

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1754
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1816
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1848
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1770
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1771
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1566
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1844
     
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1881
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1853
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1854
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1862

Released

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

AOB


New Issues

Added to sprint

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1881
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1852
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1887
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-1704

Not added to sprint

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

Other