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 expect version are working on 3.1.0 will already have been released around Tuesday, March 28. After that, we will proceed with 3.1.12-SNAPSHOT to do bug fixes, performance, security, & refactoring.
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2158 |
---|
|
(The approach described in the comments seems correct — as long as the service validates and is the absolute source of information, that all goodalso impacts UI) Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-1979 |
---|
|
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-1780 |
---|
|
(is this worth doing? enough benefit?) Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-1391 |
---|
|
(is this worth doing? enough benefit?)
Reference Data
- (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?(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.)
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-21851695 |
---|
|
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-1696 |
---|
|
(Needs description)
Stretch:
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-16951444 |
---|
|
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-1696 |
---|
|
??? Geo data ??? (
UI
Bugs
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-1444 |
---|
|
) Josh to follow up if we need this
UI
...
- (MUST)
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2137 |
---|
|
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-21262156 |
---|
|
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-22032142 |
---|
|
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-21032161 |
---|
|
(Q: Which screen are we talking about? Is it administration programs?) Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-21372223 |
---|
|
New Stuff
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-21562140 |
---|
|
Must Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-21422242 |
---|
|
Must Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-21612216 |
---|
|
Must Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-21842188 |
---|
|
Must Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2216 |
---|
|
...
- Added on 4/3/17 as a MUST
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-12712037 |
---|
|
(Should we remove this? Sam has broken out multiple stories for rolesPrioritize 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.) Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-21402215 |
---|
|
First Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2141 |
---|
|
- New user setup and administration - Need to talk about workflow with modals (Nick and Sam)
- ??Other administration screens?? Second
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2190 |
---|
|
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?)
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2107 |
---|
|
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2037 |
---|
|
(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)
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-1609 |
---|
|
(Nick to simplify this ticket)
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2045 |
---|
|
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-19252066 |
---|
|
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-16092164 |
---|
|
(Nick to simplify this ticket) Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2165 |
---|
|
- Migrate other modals to use OpenLMISModalService (check if has been fixed already)
Stretch Goals
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2045-1682 |
---|
|
Dev-UI
- Make watch build just files that changed
- Add Live Reload
Platform
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2066-1972 |
---|
|
- or 9.6- MUST
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
2188 - Migrate other modals to use OpenLMISModalService
...
- (ill)
- MUST
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
1682
Dev-UI
- Make watch build just files that changed
- Add Live Reload
Nick - are 1907 and 1908 a priority?
...
- (ill)
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2233 |
---|
|
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2232 |
---|
|
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2155 |
---|
|
should this go into the sprint? What component?
...
Service Util
Release 3.0.1. Next is 3.0.2-SNAPSHOT
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-1972 |
---|
|
...
Notification Service
Stretch:
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS- |
---|
|
...
- (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??
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-14441853 |
---|
|
(Josh following up) Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2111 |
---|
|
(Might be too big for this sprint)
...
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2167 |
---|
|
– 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
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2113 |
---|
|
– 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) Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2166 |
---|
|
(any follow-up needed?)- WAIT
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-1997 |
---|
|
(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) Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2162 |
---|
|
or Assign to Sam Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2160 |
---|
|
or similar? Assign to Sam Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2168 |
---|
|
- Wiki Clean-up:
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2200 |
---|
|
and Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2201 |
---|
|
(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
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?:
-
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-2232 |
---|
|
...
Jira Legacy |
---|
server | JIRA (openlmis.atlassian.net) |
---|
serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
---|
key | OLMIS-1693 |
---|
|