Versions Compared

Old Version 7

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-09-14 ERM Weekly Delivery Update
ReferencesJIRA Issue Board

Goals

Participants

Apologies

  • Peter Boehm

Discussion items

Time

Item

Notes

<5 minsIntroductions

Call Priorities
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2336
    • John Coburn is looking at syncing cleared filters from the location
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2344

To pick up in mid-sprint review on Monday

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

WIP 

Expand
titleIn 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

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2279
    • Progress / Impediments: Just started
    • TODO: all
    • New unknowns / help or input needed: NA
    • ETA for review: 
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2347

    • Progress / Impediments: 
      • PR raised
      • no label, just value for identifiers
      • tests extended
    • TODO: 
      • switch type and identifier column
    • New unknowns / Help or input needed: NA
    • ETA for review: Today
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2351
    • Progress / Impediments: 
      • Cannot determine why the PO lines return is empty as PO line is always empty if no permission, so "No PO lines message is shown" ... however, should know permission without retrieving PO lines
    • TODO: 
      • root out where PO lines array content is suppressed by ERM backend
      • refactor depending on whether array is empty or not
    • New unknowns / Help or input needed
    • ETA for review: Today
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2352
    • Progress / Impediments: Done
    • TODO: push for code review
    • New unknowns / help or input needed: NA
    • ETA for review: Today

Pending

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


Expand
titleNeeds 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?


Expand
titleSprint 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-2336

Needs Elaboration

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

Sprint Backlog - Next Up

  • Claudia: ?
  • Ethan: 
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-2307
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-2311
  • Monireh:  
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-2279
  • Peter: ?
  • Owen
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-2332
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-2334



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

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2348
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2353
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2349
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2355

Sprint Backlog -  At Risk

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

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-2214
    • back for development
    • needs to be redone for SKC 3.0

QA / UAT 

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

Bugfix Cycle 

  • NA



Release Candidates

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

For Release / Pending Testrails

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2289
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2313
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2306
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2309
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2308
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2314
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2330
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2339

Closed: Nolana R2022.3

Stories / Bugs

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

RTL / Tasks

  • NA

Previously

Closed (No ERM Release)

  • NA
  • <10 mins

AOB


New Issues

Added to sprint

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

Added to sprint

Not added to sprint

  • NA

Other

  • SKC is at 3.0, so workspace and local environments should be nuked/updated
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-2314

    • dismissable UI message in Scenario 7 not delivered
    • need to find a good way to determine how many users are affected
    • need a pattern for communicating changes that affect multiple users without adding noise
    • to be handled separately from the rest of ERM-2314, which is ready to release