<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 JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2886 |
---|
|
- 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
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | SI-12 |
---|
|
- Progress / Impediments:
- TODO:
- resolve github actions warning
- remove slash in line 75
- New unknowns / Help or input needed:
- ETA for review: today
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2630 |
---|
|
- 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 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 Up Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2883 |
---|
|
- 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
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1026 |
---|
|
- 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
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1061 |
---|
|
- "Load all" button outside of MCL is not feasible
- Jump to top and jump to bottom is doable
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1795 |
---|
|
Allocations- Claudia:
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1026 |
---|
|
- Monireh:
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1061 |
---|
|
- 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 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:QA / UAT Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2879 |
---|
|
- needs environment to be re-built
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2064 |
---|
|
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2612 |
---|
|
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2633 |
---|
| / Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2624 |
---|
| / Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2625 |
---|
|
|
| Release Candidates - What has passed QA since last dev call?
- What has been closed since last dev call?
| For Release / Pending Testrails Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2506 |
---|
|
Closed: Poppy R2023.2Stories / BugsMaintenance / TasksRelease TasksClosed: Orchid R2023.1 Bugfix Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2643 |
---|
|
Release TasksClosed (No ERM Release) |
| AOB
| New Issues Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | BF-464 |
---|
|
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2884 |
---|
|
Added to sprint Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2883 |
---|
|
Not added to sprint Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2885 |
---|
|
OtherComponent UpdatesRelease PlanningTestingSecurity |