| <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-2937 |
|---|
|
- Progress / Impediments:
- TODO:
- need to double check our implementation and see if we can get this working without the labelling
- then revert to JC / #stripes
- need to reconcile inconsistency of pagination across FOLIO apps, and anti-pattern of importing from acquisitions
- New unknowns / Help or input needed: NA
- ETA for review: NA
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-2421 |
|---|
|
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-2934 |
|---|
|
|
| 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)?
| Blocked| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-2923 |
|---|
| / | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-2939 |
|---|
|
- Progress/Impediments:
- required bubbling hierarchy update, which is tricky with Grails save handling of save
- identified what appeared to be a non-standard double-saving code block that has been moved to event listener - appeared to work, but broke ingest when merged
- currently only bubbles 1 step up or down, rather than full tree
- last updated increasingly proving to be the wrong field for this
- TODO:
- merge frontend changes for ERM-2923
- revert changes in listener from ERM-2939
- then review what the goal for coverage and last updated and re-engineer an appropriate solution as part of UXPROD-4272 & UXPROD-4271 (Owen) and review with team+Steve
- New unknowns / help or input needed: NA
- ETA for review: today
Needs Elaboration / TriageSprint Backlog - Next UpAllocations - Claudia:
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-2922 |
|---|
|
- options
- maybe decouple search from SAS so it goes into the url and then fill the box from the url?
- Ethan:
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-2630 |
|---|
|
- Jack:
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-2421 |
|---|
|
- returned to dev for e2e testing
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-2934 |
|---|
|
- enum and display column changes made
- need labels adding
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-1110 |
|---|
|
|
| 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 Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-2940 |
|---|
|
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-2630 |
|---|
|
Sprint 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-2641 |
|---|
|
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| 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 JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-2929 |
|---|
|
- awaiting Nolana (ERM-2932) environments rebuild for testing
- raised to Oleksii for action
Pending Testrails
Closed: Nolana CSP
Stories / Bugs| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-2938 |
|---|
|
Maintenance / TasksRelease TasksClosed (No ERM Release) |
| AOB
| New Issues | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-2941 |
|---|
| / | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-2942 |
|---|
|
- undergoing triage by k-int
- Slack conversation group
- possibly related to reference environment build issues
- Raised as P2 - not really clear why
Added to sprintNA| Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | ERM-2812 |
|---|
|
Not added to sprintOtherComponent UpdatesRelease PlanningTestingSecurity |