<5 mins | Introductions | |
| Call Priorities | |
| WIP Expand |
---|
| - 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 Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2641 |
---|
|
- 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
Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2923 |
---|
|
- 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
Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2934 |
---|
|
- Progress / Impediments:
- TODO:
- New unknowns:
- Help or input needed:
- ETA for review:
Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2937 |
---|
|
- Progress / Impediments:
- TODO:
- New unknowns:
- Help or input needed:
- ETA for review:
|
| Pending Expand |
---|
| - ISSUE
- Blocking conditions
- Action needed
|
- Are the blocking conditions still relevant?
- What action is needed to unblock, and by whom?
Expand |
---|
| - 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:
Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2937 |
---|
|
- Ethan:
Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | SI-23 |
---|
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2630 |
---|
|
- 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: Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2421 |
---|
|
QA / UAT Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2935 |
---|
| resolved. moving to closed. Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | SI-23 |
---|
|
|
| Release Candidates - What has passed QA since last dev call?
- What has been closed since last dev call?
| For Release / Awaiting Deployment Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2929 |
---|
| 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) Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2790 |
---|
| Updated to 4.7.0
Maintenance / TasksRelease TasksClosed (No ERM Release) Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-29112935 |
---|
|
|
| AOB
| New Issues Added to sprint Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | SI-23 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2938 |
---|
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2937 |
---|
|
Not added to sprintOtherComponent Updates- SKC 4.7.0 has been released with a new ComboButton componentNA
Release Planning- Partial release candidates should be determined before adding Grails 5 upgrade NA
TestingSecurity |