Versions Compared

Old Version 9

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-10-27 ERM Weekly Delivery Update
ReferencesJIRA Issue Board

Goals

Participants

Apologies

Discussion items

Previous Actions

Time

Item

Notes

<5 minsIntroductions

Call Priorities
  • Jira Legacy
    serverSystem JIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1899
  • Jira Legacy
    serverSystem JIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1687
  • Jira Legacy
    serverSystem JIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1915
  • Jira Legacy
    serverSystem JIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1850
  • Jira Legacy
    serverSystem JIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1902
  • RTL /
    Jira Legacy
    serverSystem
Jira
  • JIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-
1913
  • 1661
    • 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

  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1850
    • 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
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1902
    • 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
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1488
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1492
    • PR depends on changes made yesterday to stripes-erm-components
    • will wait for those to avoid jenkins fail
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1662
    /
    Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1664

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 Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1687
    • Updated following UX/Dev discussion
    • Current work done by Claudia is necessary but not sufficient
    • TODO: 
      • QA on ERM-1899 (PO)
      • Push validation changes made so far (Dev), with scope caveat (UX)
      • Add new issue re focus handling following screen reader recommendations review (UX)
      • 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:  
    • Jira Legacy
      serverSystem JiraJIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1906
    • Jira Legacy
      serverSystem JiraJIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1907
  • Ethan:
    • Jira Legacy
      serverSystem JiraJIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1900
    • Jira Legacy
      serverSystem JiraJIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1883
  • Adi:
    • Jira Legacy
      serverSystem JiraJIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1915
      • 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.  
        • Owen to add sample set to bugfest environment once 5.0.4 change is built
      • Components: 
        • multiple routes
      • Estimate: longer to verify ... 2d max
    • Jira Legacy
      serverSystem JiraJIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-1913
  • 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

  • NA

Sprint Backlog -  At Risk

  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1904
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1661
Sprint Backlog -  At Risk
  • 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 Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1467
    /
    Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1468
    /
    Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1472
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1257
    /
    Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1269
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1490
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1491

QA / UAT 

  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1899
    • 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
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1882
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1884

Bugfix Cycle 

  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1914



Release Candidates

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

Accepted

Need testrails cases

  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1688
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1791
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1888
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1813

Closed: Lotus R1 2022

Features

  • NA

RTL / Other Tests

  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1474
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1289
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1282
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1852
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1901

Closed: Kiwi R3 2021 Bug Fix

  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1892
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1903
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1916
<10 mins

AOB


New Issues

Added to sprint

  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1914
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1915
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1906
    /
    Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1907

Not added to sprint

  • NA

Other

  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1913
  • Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-1916