: 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.
(also impacts UI)
(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.) (Are there any tickers for this?) (Paweł Gesek Yes, please make a ticket for this one if Josh doesn't get to it today. It should be marked Blocker.)
(Needs description)
Stretch:
UI
Bugs
(MUST)
(Q: Which screen are we talking about? Is it administration programs?)
Must
Must
Must
Must
Added on 4/3/17 as a MUST
(Prioritize sooner for Mary Jo for Malawi)
These stories have dependencies on each other and must be done in order: 2215, then 2189 and last 2190. (Nikodem Graczewski: Those tickets does not look like they have to be done in order, those are separate screens.)
First
Second
Third (Q1: Do we want to stick to the modal approach? Wouldn't new screen make more sense in this case? The form is getting quite big. Q2: Are there any Role types on the back-end? Aren't types only related to Rights?)
(Nick, I just found this marked fixVersion=3.0.1...moved it to 3.0.2 now, but is it important?)- Make ticket for: Designing select all/none – get passed through PC – ILL (repeated below under Team ILL)
(Nick to simplify this ticket)
- 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
- or 9.6- MUST
(ill) - MUST
(ill) 
Service Util
Release 3.0.1. Next is 3.0.2-SNAPSHOT
Notification Service
Stretch:
(we said we'd pick this up if team tower of power is looking for work - if picked up, this will move Notification service to working on 4.0.0 instead of 3.0.1)
Component leads, are any of the following time sensitive or still needed??
(Might be too big for this sprint)
(is this ILL or SolDevelo?) — Josh and Chongsun to talk about)
Team ILL
– Need to define the tech persona for this (can they find their IP address and edit a .env file
- Moved from UI: Make ticket for: Designing select all/none – get passed through PC – ILL
Grooming call thinks the following isn't needed for patch release, but planning for month of April is needed
- WARNING
– 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) 
(any follow-up needed?)- WAIT
(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) 
Assign to Sam 
Assign to Sam
- Wiki Clean-up:
and 
(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)
there are lots of ideas from the Holding Off section at the bottom of Backlog Grooming Sprint 22
PLUS there are issues marked fixVersion=3.0.2 that were previously 3.0.1 and are not reflected above on this page. Are these important?: