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
Version 1
Next »
Discussion items
Time | Item | Notes |
---|
<5 mins | Introductions | |
| Call Priorities | |
| 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-2641
-
Getting issue details...
STATUS
- Progress / Impediments:
- documentation query resolved - no action needed
- no Orchid CSP requirement, so clear to merge
- TODO:
- New unknowns: NA
- Help or input needed: NA
- ETA for review: today
-
ERM-2923
-
Getting issue details...
STATUS
- Progress/Impediments:
- every time to delete / add new coverage, a multiplying loop is happening at the backend
- moving the saves around isn't making a difference
- cross-checking coverage calculation in title instance to suppress update isn't making a difference
- coverage update still traveling up hierarchy
- changeListener is happening before update, not downstream after update is saved
- coverage update appears to be staggered by one update
- TODO:
- check coverage list equality in setCoverageFromSchema; if equal, don't save
- verify that the broken behaviour on master for a potential new bug
- QA using files adapted from ERM-850
- New unknowns: NA
- ETA for review: next week
|
| 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?
- Who is picking up what next?
- When is next issue expected to start / complete?
- Anything needed to start next issue (dependencies or clarifications)?
| BlockedNeeds Elaboration / TriageSprint Backlog - Next UpAllocations - Claudia:
-
ERM-2937
-
Getting issue details...
STATUS
- Ethan:
-
SI-23
-
Getting issue details...
STATUS
-
ERM-2630
-
Getting issue details...
STATUS
- Jack:
|
| 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 followSprint Backlog - At Risk Removed |
| In Review - Any impediments to review or QA?
- Any useful context, implementation choices or limitations for the reviewer/tester to know ?
| Code Review:-
ERM-2421
-
Getting issue details...
STATUS
QA / UAT -
ERM-2935
-
Getting issue details...
STATUS
- resolved. moving to closed.
|
| Release Candidates - What has passed QA since last dev call?
- What has been closed since last dev call?
| For Release / Awaiting Deployment-
ERM-2929
-
Getting issue details...
STATUS
- is actually on master for Poppy
- resolved for Orchid (ERM-2933)
- awaiting Nolana (ERM-2932) environments rebuild for testing
Pending Testrails
Closed: Nolana CSP
Stories / BugsMaintenance / TasksRelease TasksClosed (No ERM Release) -
ERM-2790
-
Getting issue details...
STATUS
-
ERM-2911
-
Getting issue details...
STATUS
|
| AOB
| New Issues Added to sprint-
SI-23
-
Getting issue details...
STATUS
-
ERM-2938
-
Getting issue details...
STATUS
-
ERM-2937
-
Getting issue details...
STATUS
Not added to sprintOtherComponent Updates- SKC 4.7.0 has been released with a new ComboButton component
Release Planning- Partial release candidates should be determined before adding Grails 5 upgrade
TestingSecurity |