...
- 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.)
- 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)
(Question in comments)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-1695
(Needs description)Dispensable facility approved products seeJira 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 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-2136
Stretch:
Josh to follow up if we need thisJira Legacy server JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-1444 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-2236
...
MustJira Legacy server JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2140
MustJira 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-2242
MustJira 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
MustJira 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
Added on 4/3/17 as a MUSTJira 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-2267
(Prioritize sooner for Mary Jo for Malawi)Jira Legacy server JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2037
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.)
FirstJira 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-2215
SecondJira 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-2189
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) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2190
...
- or 9.6Jira Legacy server JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-1972 - Write proposal for ad-hoc reports for PC and TC (ill)
- Component diagram for routine reports (ill)
- MUST
(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-2250 - MUST
2078Jira 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-
(ill)2251 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-2180
...
Jira Legacy server JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2155
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)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-1751
Component leads, are any of the following time sensitive or still needed??
...