Page History

...

ERM Sprint 119

Participants

Apologies

Discussion items

Time

Item

Notes

Action Items

<5 mins

Introductions

Attendees / Apologies
Upcoming Availability

Previous Actions

NA

In Review

Code Review:

Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1772
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1773
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1757
/
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1758
/
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1759
/
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1760
/
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1761
- Separate PR to break dependency on blocked until
  - STCOM-865 is resolved and
  - waiting for user feedback for minimal set of shortcuts
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1781
waiting for feedback from Steve - on leave, returning from 2 Aug

QA / UAT

Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1697
- needs a running environment that isn't snapshot with knowingly broken
- reassigned to Owen for testing
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1600
/
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1601
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1656

WIP

In Progress

Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1731
- expected for code review by end of week
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1774
- work done
- once release of ui-licenses is done, can be pushed to PR
- still stymied by issue around running integration tests
  - though this may not be touched by integration tests
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1283
- BigTest tests replaced
  - aside: wouldn't necessary replace BigTests, if they are integration tests
- TODO: add new tests

Pending

Sprint Backlog

Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1647
- TODO:
  - add post-spike tasks / requirements
  - expected to be ready for next sprint
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1648
- TODO:
  - add option for 'Today'
  - add aria-labels
  - info popover
- but to wait until user feedback
- → blocked
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1261

Needs Elaboration / Bugfix Cycle / Blocked

Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1775

Release Candidates

Accepted

Needs to be added to Bugfix post-release

Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1777
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1767

Closed

Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1001
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1145
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1765
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1231
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1540
/
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1541
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1702
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1755

<10 mins

AOB

New Issues

Added to sprint

Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1261
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1790
/
- next up, pending vagrant
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1789
- needs help from ianibbo to run integration tests (hardware issues)

Not added to sprint

NA

Other

Stripes v7 Upgrade
- what needs to happen to compete complete the upgrade?
  - test out branch
  - bump dependencies to v7 so they can make reference environment / CI builds
- what do devs need to do for environments and WIP?
  - Adi to review and test v7 pre-alpha build and provide feedback to stripes
  - no action needed from other developers until released and dependencies bumped
- how early or late should we schedule this?
  - to verify as early as possible
  - to bump dependencies and merge to master in sprint 123
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1793
- stripes-acq-components on platform-erm
- can this be removed?
- need to verify impact on translations / orders, but yes, in theory it should
Jira
server FOLIO Issue Tracker
serverId 6ccf3fe4-3301-368a-983e-20c466b11a49
key ERM-1794
- potentially can wait until stripes v7 upgrade
- Adi to verify that the existing dependency resolution will not be pulled before Kiwi/Lotus

Space shortcuts

Child pages

Versions Compared

Old Version 2

New Version Current

Key