Skip to end of banner
Go to start of banner

2023-03-22 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 2 Next »

Meeting Details

Date
 
Time

11:30am UK, 12:30pm Germany

Location

Video Call in

Previously2023-03-15 ERM Weekly Delivery Update
ReferencesJIRA Issue Board

Goals

Participants

  •  

Apologies

Discussion items

Time

Item

Notes

<5 minsIntroductions

Call Priorities
  • SI-12

WIP 

 In Progress
  • ISSUE: 
    • Progress / Impediments: 
    • TODO: 
    • New unknowns: 
    • Help or input needed: 
    • ETA for review: 
  • 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-2886 - Getting issue details... STATUS
    • Progress / Impediments: 
      • pattern was not matching
      • clarified with PO
    • TODO: un-draft PR
    • New unknowns / Help or input needed: NA
    • ETA for review: ready to go
  • SI-12 - Getting issue details... STATUS
    • Progress / Impediments: 
      • PR raised
    • TODO: 
      • resolve github actions warning
      • remove slash in line 75
    • New unknowns / Help or input needed: 
    • ETA for review: today
  • ERM-2630 - Getting issue details... STATUS
    • Progress / Impediments: 
      • Discussed logging with Owen
      • Will follow logging for old process (so can be applied to both)
      • logging work pushing back refactoring
      • switch to decide whether harvest or pushKb is now in place, operating at service level
      • delayed by cypress calls
      • Developer workflow / reset environments (from Ian)
    • TODO: 
      • some questions to take to users
        • OS to discuss with GBV
        • Martina to set up call 
        • To take forward separate (out of scope) to ERM-2630
      • align new logging with existing jobs 
      • followed by title ingest refactoring
      • update ERM-2631 with summary from conversation notes
    • New unknowns: NA
    • Help or input needed: 
      • Developer workflow / reset environments (from Ian)
        • further discussion needed about how to implement
        • needed for ERM-2631

Pending

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


 Needs Elaboration
  • ISSUE: 
    • Who / When: 
    • ETA Ready for Dev: 
  • 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

  • NA

Needs Elaboration / Triage

  • NA

Sprint Backlog - Next Up

  • ERM-2883 - Getting issue details... STATUS
    • update route to be more specific: if `erm_id`, only redirect if rendering list (ie, nothing open in third pane)
    • will change existing behaviour 
    • returned to Owen for elaboration
    • moved out of sprint
  • ERM-1026 - Getting issue details... STATUS
    • coming from compare.gson being pulled from backend - different approach could be refdata or strings 
      • refdata:
        • could be harder
        • if so, erm-comparisons should have a picklist editor
      • strings
        • use as translation keys
  • ERM-1061 - Getting issue details... STATUS
    • "Load all" button outside of MCL is not feasible
    • Jump to top and jump to bottom is doable
      • stripes button type text
  • ERM-1795 - Getting issue details... STATUS

Allocations

  • Claudia: 
  • Monireh: 
  • Ethan: 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 - to follow

Sprint Backlog -  At Risk

Removed

  • NA

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 

  • ERM-2879 - Getting issue details... STATUS
    • needs environment to be re-built
  • ERM-2064 - Getting issue details... STATUS
  • ERM-2612 - Getting issue details... STATUS
  • ERM-2633 - Getting issue details... STATUS / ERM-2624 - Getting issue details... STATUS / ERM-2625 - Getting issue details... STATUS

Release Candidates

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

For Release / Pending Testrails

Closed: Poppy R2023.2

Stories / Bugs

  • NA

Maintenance / Tasks

  • NA

Release Tasks

Closed: Orchid R2023.1 Bugfix

Release Tasks

  • NA

Closed (No ERM Release)

  • <10 mins

AOB


New Issues

  • BF-464 - Getting issue details... STATUS
  • ERM-2884 - Getting issue details... STATUS

Added to sprint

Not added to sprint

Other

Component Updates

  • NA

Release Planning

Testing

Security

  • No labels