<5 mins | Introductions | |
| Call Priorities |
|
|
|
|
| WIP - 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-1850 |
---|
|
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1953 |
---|
|
- moved acqMethods to new folder
- created new mock and tests
- tests should be fine, but not mocks with okapiKY (locally)
- stripes-config in stripes-core
- TODO
- get rid of stripes repos locally
- call stripes-core and -components remotely, not locally
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1973 |
---|
|
- not able to diagnose
- resources not being fetched
- endpoints not being called
- seems to be when editing and viewing interfaces
- need to navigate away and then return
- possible routes:
- fetch line with hasInterface == 2.0 conditional may need to be TRUE'd
- parameters:
- maybe throwing an error will yield a different fail
- relies on
- permissions check: unlikely unless these changed since implementing (post-Iris, pre-Juniper)
- if neither, then should seek further input rom stripes
- Future Option:
- move interfaces over to use react-query to fetch data as and when needed, though doesn't address manifest issue, if there is one. NOT to be done now.
|
| Pending Blocked - Are the blocking conditions still relevant?
- What action is needed to unblock, and by whom?
Needs Elaboration - 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?
Sprint Backlog - 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-1941 |
---|
|
- effectively blocked by
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | FOLIO-3362 |
---|
|
Needs ElaborationSprint Backlog - Next Up- Claudia:
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-19741976 |
---|
|
- Ethan:
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1799 |
---|
|
- Monireh:
- Peter: TBD
|
|
|
|
| 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-1923 |
---|
| / Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1920 |
---|
|
- need to go back to verify that this is at ERM end
Sprint Backlog - At Risk Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-17991938 |
---|
|
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-19381974 |
---|
|
- has similar technical to ERM-1973
|
| 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 JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1293 |
---|
|
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1301 |
---|
|
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1744 |
---|
|
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1745 |
---|
|
QA / UAT Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1931 |
---|
|
- small change to web-toolkit
- need to QA issue but also keep an eye on impact on hosted-ref-env, including performance
- to monitor prior to full release
Bugfix Cycle
|
| Release Candidates - What has passed QA since last dev call?
- What has been closed since last dev call?
| Closed: Lotus R1 2022Features Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1762 |
---|
|
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1949 |
---|
|
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1950 |
---|
|
RTL / Other Tests Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1300 |
---|
|
|
<10 mins | AOB
| New IssuesAdded to sprint Not added JiraJIRA | serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1976 |
---|
|
Not added to sprint Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1977 |
---|
|
OtherGOKb XML Issue - is this confirmed fixed?
- any issue to develop/test going forward?
- not so much ... more a question of whether we want to present better visibility or failure reporting to devops or other interested users.
GitHub Actions - got a GA YAML file based on other modules on a branch for ERM
- pending merge
- can run parallel to Jenkins
- applying to ui-agreements
|