<5 mins | Introductions | |
| Call Priorities | -
ERM-2645
-
Getting issue details...
STATUS
- Owen to test using Cypress
- Needs non-prod environment to run Cypress on against these tests
- Followups:
|
| 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-2630
-
Getting issue details...
STATUS
- Progress / Impediments:
- expecting some external service to use Gokb scrollAPI in chunks of 5000 packages (not content items), managing state and queue position
- treating cursor/state as black box for now
- should be able to use schemas/shapes mostly as-is
- add package id to contentSchema
- add comment t
- will end up with 2 parallel ways to get data in
- scheduled harvest for package ingest (current)
- push service (this piece)
- will need to refactor package ingest (harvest) service to separate out reusable ingest functionality
- support either harvest or push (not both) for an ingest
- external push service will use TIPPs to set up content items, linking them to known content rather than creating new ones
- provides transactional redundancy
- provides a restart point
- reduce performance burden on agreements
- so far:
- 2 trivial endpoints set up under `erm/pushkb`
- TODO:
- get endpoints accepting/logging out json input
- started
- not wired through okapi as shape uincertain
- can hit locally, passsing list of packages and log them out to a package schema
- therefore package schema is accepting this approach
- split schema to interdependently (1) expect and (2) not expect ...
- wire schema into ingest process
- dig into ingest process to plan refactoring
- New unknowns:
- Help or input needed:
- Input needed from Ian to understand legacy technical decisions around, eg, remote kb, source/ref push/pull
- To follow up on Thursday with Ian re domain model and shape of future shape/behaviour of external service
- ETA for review:
-
ERM-2612
-
Getting issue details...
STATUS
- Progress / Impediments:
- passed to code review
- needs test data to be relocated to central file
- TODO:
- Ethan to stub new Jira for multiselect and delete ERM-2612
-
ERM-2664
-
Getting issue details...
STATUS
- New unknowns / Help or input needed: NA
- ETA for review: now
|
| 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)?
| Blocked-
ERM-2645
-
Getting issue details...
STATUS
- OS to ask Khalilah and hosted-ref-environments
Needs Elaboration / TriageSprint Backlog - Next Up-
ERM-2643
-
Getting issue details...
STATUS
Allocations- Claudia:
-
ERM-2643
-
Getting issue details...
STATUS
- Ethan:
- Release Tasks
-
ERM-2640
-
Getting issue details...
STATUS
-
ERM-2648
-
Getting issue details...
STATUS
-
ERM-2649
-
Getting issue details...
STATUS
-
ERM-2643
-
Getting issue details...
STATUS
- Monireh:
-
ERM-2612
-
Getting issue details...
STATUS
|
| 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-2633
-
Getting issue details...
STATUS
-
ERM-2612
-
Getting issue details...
STATUS
- refdata for tests need to be removed from test resources and added to central test data file
-
ERM-2624
-
Getting issue details...
STATUS
-
ERM-2625
-
Getting issue details...
STATUS
-
SI-12
-
Getting issue details...
STATUS
- found it requires opening in a new window
- pushed to QA
QA / UAT -
ERM-2506
-
Getting issue details...
STATUS
|
| Release Candidates - What has passed QA since last dev call?
- What has been closed since last dev call?
| For Release / Pending TestrailsClosed: Poppy R2023.2Stories / BugsMaintenance / TasksRelease TasksClosed: Orchid R2023.1-
ERM-2626
-
Getting issue details...
STATUS
Closed: Orchid R2023.1 Bugfix-
ERM-2642
-
Getting issue details...
STATUS
Closed (No ERM Release) |
| AOB
| New Issues - New unexpected Proxy Settings behaviour
- If no proxy setting set, prompts for unsaved changes when navigating away
- handleCancel → onDelete → onDelete
- needs logic to reset form if field length < 1
- remove onDelete call from handleCancel
- However, better to rewrite away from Card to MCL
-
ERM-2793
-
Getting issue details...
STATUS
-
ERM-2792
-
Getting issue details...
STATUS
Added to sprint-
ERM-2647
-
Getting issue details...
STATUS
/
SI-12
-
Getting issue details...
STATUS
-
ERM-1795
-
Getting issue details...
STATUS
Not added to sprint-
ERM-2644
-
Getting issue details...
STATUS
-
ERM-2792
-
Getting issue details...
STATUS
-
ERM-2793
-
Getting issue details...
STATUS
Other- Owen and Gill to review potential UX consistency issues to bring into release cycle
Component UpdatesRelease Planning- Orchid Bugfix tests to follow ERM-2643
Testing- describe permissions as part of test scenarios
Security |