MJ Note : Discussed releasing another patch release at the end of this sprint as well. This will allow us one more sprint to get in needed extension points, bugs and more admin screens. Please keep this in mind when planning for sprint 23.
Requisition
We are working on 3.1.2-SNAPSHOT to do bug fixes, performance, security, & refactoring.
- - OLMIS-2158Getting issue details... STATUS (also impacts UI)
- - OLMIS-1979Getting issue details... STATUS (please advise if it impacts UI or other components)
Reference Data
Working toward v5.0.0 - breaking changes in the commodity model endpoints
- Lot Management API endpoints (Stock Team Panda needs this ASAP! Josh Zamor We have this wiki page that maps out proposed Lot Management endpoints, but we need your review and we need to turn this into tickets for Teams AYIC/TOP to code as a top priority after 3.0.1 ref-distro release.)
- Any other bugs or issues Pengfei had with ReferenceData endpoints that need to change for Stock to proceed? Josh doesn't see any, will check tonight (Thur night)
- - OLMIS-1695Getting issue details... STATUS
- - OLMIS-1696Getting issue details... STATUS
- Dispensable facility approved products see - OLMIS-2136Getting issue details... STATUS
Stretch:
- - OLMIS-1444Getting issue details... STATUS Josh to follow up if we need this
-
-
OLMIS-2236Getting issue details...
STATUS
UI
Bugs
- - OLMIS-2219Getting issue details... STATUS (MUST)
- - OLMIS-2137Getting issue details... STATUS
- - OLMIS-2156Getting issue details... STATUS
- - OLMIS-2142Getting issue details... STATUS
- - OLMIS-2161Getting issue details... STATUS
- - OLMIS-2223Getting issue details... STATUS
New Stuff
- - OLMIS-2140Getting issue details... STATUS Must
- - OLMIS-2242Getting issue details... STATUS Must
- - OLMIS-2216Getting issue details... STATUS Must
-
-
OLMIS-2188Getting issue details...
STATUS
Must
These stories have dependencies on each other and must be done in order: 2215, then 2189 and last 2190. - - OLMIS-2215Getting issue details... STATUS First
- - OLMIS-2189Getting issue details... STATUS Second
- - OLMIS-2190Getting issue details... STATUS Third
- - OLMIS-2107Getting issue details... STATUS
- - OLMIS-2037Getting issue details... STATUS
- Make ticket for: Designing select all/none – get passed through PC – ILL
- - OLMIS-2045Getting issue details... STATUS
-
-
OLMIS-2066Getting issue details...
STATUS
- Migrate other modals to use OpenLMISModalService (check if has been fixed already)
Stretch Goals
Dev-UI
- Make watch build just files that changed
- Add Live Reload
Platform
- - OLMIS-1972Getting issue details... STATUS - or 9.6
- Write proposal for ad-hoc reports for PC and TC (ill)
- Component diagram for routine reports (ill)
- - OLMIS-2078Getting issue details... STATUS (ill)
- - OLMIS-2233Getting issue details... STATUS
- - OLMIS-2232Getting issue details... STATUS
- - OLMIS-2180Getting issue details... STATUS
Service Util
Release 3.0.1. Next is 3.0.2-SNAPSHOT
Component leads, are any of the following time sensitive or still needed??
- OLMIS-1853Getting issue details... STATUS
- OLMIS-2111Getting issue details... STATUS (Might be too big for this sprint)
- OLMIS-2074Getting issue details... STATUS
- OLMIS-1707Getting issue details... STATUS
- OLMIS-1994Getting issue details... STATUS (is this ILL or SolDevelo?) — Josh and Chongsun to talk about)
Team ILL
- - OLMIS-2167Getting issue details... STATUS – Need to define the tech persona for this (can they find their IP address and edit a .env file
Grooming call thinks the following isn't needed for patch release, but planning for month of April is needed
-
-
OLMIS-2113Getting issue details...
STATUS
– Not critical for patch release – Should figure out when we need it by and work backward
(Team ILL; Brandon is willing to write up/diagram a few options and bring to a group conversation including Team Panda, Josh, Mary Jo) - - OLMIS-2166Getting issue details... STATUS (any follow-up needed?)
- - OLMIS-1997Getting issue details... STATUS (we explained versioning to Tech Committee and SolDevelo, but we should update the wiki to capture it—especially that the components are semantically versioned, but the ref-distro uses milestone version numbers; and document that we prefer to coordinate working on master towards one common goal, namely the next release, in order to avoid the added effort of branching; Brandon has some paper notes and is willing to write a draft, but I believe it would really be Josh and Tech Committee that would finalize/approve)
- - OLMIS-2162Getting issue details... STATUS or - OLMIS-2160Getting issue details... STATUS or similar?
- - OLMIS-2168Getting issue details... STATUS
- Wiki Clean-up: - OLMIS-2200Getting issue details... STATUS and - OLMIS-2201Getting issue details... STATUS (and Mary Jo and Tenly have other wiki work it may be helpful to track)
- Need to discuss with Mary Jo: go back and adjust how OLMIS-1911 is implemented to be more in line with 1.x and 2.x so future migrations will be smoother (Josh and Brandon raised this)
Plus there are lots of good ideas from the Holding Off section at the bottom of Backlog Grooming Sprint 22