Skip to end of banner
Go to start of banner

2021-11-03 ERM Weekly Delivery Update

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Current »

Meeting Details

Date

 

Time

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

Location

Video Call in

Previously2021-10-27 ERM Weekly Delivery Update
ReferencesJIRA Issue Board

Goals

Participants

Apologies

Discussion items

Time

Item

Notes

<5 minsIntroductions

Call Priorities
  • ERM-1899 - Getting issue details... STATUS
  • ERM-1687 - Getting issue details... STATUS
  • ERM-1915 - Getting issue details... STATUS
  • ERM-1850 - Getting issue details... STATUS
  • ERM-1902 - Getting issue details... STATUS
  • RTL / ERM-1661 - Getting issue details... STATUS
    • 1664 AgreementLine
    • 1681 URLCustomizer

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

  • ERM-1850 - Getting issue details... STATUS
    • TODO:
      • needs to be a criteria check
      • check hibernate docs for subquery or subcriteria implementation details
      • to test
        • manually test: find a title through clean ingest without options and search for that (before and after new code)
        • integration test: out of scope because of reliance on ingest 
      • expect for code review Thursday
  • ERM-1902 - Getting issue details... STATUS
    • Unknown: how to test in a multi-tenancy environment
    • Best approach will be monitor for breaks
    • Issue is basically done, including applying to 1883/1900
    • TODO:
      • review against current integration tests 
      • no event-related integration tests to be done (will take an additional day
  • ERM-1488 - Getting issue details... STATUS
  • ERM-1492 - Getting issue details... STATUS
    • PR depends on changes made yesterday to stripes-erm-components
    • will wait for those to avoid jenkins fail
  • ERM-1662 - Getting issue details... STATUS / ERM-1664 - Getting issue details... STATUS

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

  • ERM-1687 - Getting issue details... STATUS
    • Updated following UX/Dev discussion
    • Current work done by Claudia is necessary but not sufficient
    • TODO: 
      • QA on ERM-1899 (PO)
      • Gill and Ethan to confer on which option to progress, as defined in comments (2021-10-25)

Needs Elaboration

  • NA

Sprint Backlog - Next Up

  • Claudia: 
    • RTL
  • Peter:  
  • Ethan:
  • Adi:
    • ERM-1915 - Getting issue details... STATUS
      • to prioritise ahead of current RTL issues
      • is this possible to do at the backend?
        • doesn't look like it should be handled in the front-end
        • polling between backend modules (with a single fetch via okapi) is slow and increases fetch times rather than multiple frontend fetches (which is current expectation)
        • switching between front and back end logic is not good for a hotfix
      • best way may be to make a copy, but we're not there yet with backend storage and sync
      • strategy:
        • fix in frontend for now (live sites affected)
        • address backend storage and sync
        • apply to this and contacts
      • Frontend unknowns
        • frontend character limit is 4096, but large number of POlines would be more than this character count: therefore need multiple requests chunked across order lines :: what is the chunk break? Break at 80
        • Sending requests in series would work, but a small number (eg, 5) in parallel could work.  
        • Sample set to add once 5.0.4 change
      • Components: 
        • multiple routes
      • Estimate: longer to verify ... 2d max
    • ERM-1913 - Getting issue details... STATUS
  • Monireh: 
    • RTL

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

Sprint Backlog -  At Risk


In Review

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


Code Review: 

QA / UAT 

  • ERM-1899 - Getting issue details... STATUS
    • Tested behaviour:
      • save should be stopped, but this doesn't seem to happen
      • validation error is shown, but save is not prevented
      • if name is empty, validation prevents save
    • Correct behaviour is working locally, but not on snapshot
      • validate should be on field not form
    • Returned to Adi to raise PR with correct changes
  • ERM-1882 - Getting issue details... STATUS
  • ERM-1884 - Getting issue details... STATUS

Bugfix Cycle 



Release Candidates

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

Accepted

Need testrails cases

Closed: Lotus R1 2022

Features

  • NA

RTL / Other Tests

Closed: Kiwi R3 2021 Bug Fix

<10 mins

AOB


New Issues

Added to sprint

Not added to sprint

  • NA

Other

  • No labels