Sprint 25 is a shorter and we will release 3.0.2 on 08 May 2017 prior to the end of the release. We will release during this sprint so we will need to be mindful of what we can complete in time for a 3.0.2 patch. Note that we are still working towards 3.0.2 .
Reference UI Working towards Nikodem Graczewski (Unlicensed) ...
We're working toward openlmis-reference-ui 5.0.0-SNAPSHOT. Here's a list of all repositories and which version are being worked on:
openlmis-auth-ui - 5.0.0, next version: 5.0.1 openlmis-fulfillment-ui - 5.0.0, next version: 5.0.1 openlmis-referencedata-ui - 5.0.0, next version: 5.1.0 openlmis-report-ui - 5.0.0, next version: 5.0.1 openlmis-requisition-ui - 5.0.0, next version: 5.0.1 openlmis-ui-components - 4.0.1, next version: 4.0.2 openlmis-ui-layout - 5.0.0, next version: 5.0.1 The major version bump was due to adding main state which resulted in all the states being modified
Bugs Blockers
Jira Legacyserver JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2369
(perhaps we can pick up this sprint?) Jira Legacyserver JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2328
(wasn't picked up for 3.0.2) Jira Legacyserver JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2355
Jira Legacyserver JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2268
(wasn't picked up for 3.0.2) Critical
Jira Legacyserver JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2355
Jira Legacyserver JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2276
(wasn't picked up for 3.0.2) Jira Legacyserver JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2369
Jira Legacyserver JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2355 2414
New Jira Legacyserver JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2350
New - just to clarify, we do not want to allow any duplicates, right? Jira Legacyserver JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2238 2350
New Major
Jira Legacyserver JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2329
(wasn't picked up for 3.0.2) JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2328
Jira Legacyserver JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2224
(wasn't picked up for 3.0.2) Jira Legacyserver JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2277 2310
Jira Legacyserver JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2204 2305
Jira Legacyserver JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2295 2356
Jira Legacyserver JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2275 2268
Jira Legacyserver JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2243 2276
Jira Legacyserver JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2306 2295
Jira Legacyserver JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2352 2224
Jira Legacyserver JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2356 2309
Jira Legacyserver JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2241
MUST Jira Legacyserver JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-1889 2164
(we were not able to see this behvior, needs to be reopened) MUST Jira Legacyserver JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2383 2241
MUST Jira Legacyserver JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-1189 1889
Requisition Will be working towards 3.1.3-SNAPSHOT. Because requisition-3.1.2 is planned to be released end of April in ref-distro-3.0.2.
Jira Legacyserver JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2322
MUST (request from Malawi) Stretch Goals: Jira Legacyserver JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-1329
(Do we have to do this for 3.1??) Waiting (may be a pull request from Malawi team):This ticket does not have the current/latest design: Q: there is a ticket for an endpoint searching users, but can requisitions figure out the warehouses? I think might have to copy the logic from fulfillment here. Jira Legacyserver JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-
2321 MUST Reference Data Will be working towards 5.1.0-SNAPSHOT. Because referencedata-5.0.0 is planned to be released end of April in ref-distro-3.0.2. Improvements such as 2357 make this a Minor bump to 5.1.0, not a patch 5.0.1.
Jira Legacyserver JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2338
- MUST (blocks OLMIS-2322)Insert in second half spatial data.. Jira Legacyserver JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2370
- MUST MUST (SPLIT out OLMIS-2413 for TeamILL) Jira Legacyserver JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2280 2370
- MUST Q: Second mockup - fields are arranged in a strange way (non-style guide). Is this intentional? Q2: OLMIS-1696 changes the orderable structure. It seems this ticket does not take that into account? After the refactor, orderables do not have types, commodity types and trade items have a field with multiple orderables instead. Jira Legacyserver JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2357 2280
- MUST Jira Legacyserver JIRA (openlmis.atlassian.net)
...
...
serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-
...
- MUST Q: what about the password reset mentioned in the comments by Chongsun Ahn (Unlicensed) ?
Jira Legacyserver JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-
...
Platform Jira Legacyserver JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2232
Add in design tickets from Jira Legacyserver JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2113
Next on Ad-hoc Reporting (TeamILL) ...
Jira Legacyserver JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2379
If program data PoC should proceed:
Jira Legacyserver JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2325
Jira Legacyserver JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2324
Wait to identify next tickets from Jira Legacyserver JIRA (openlmis.atlassian.net) serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-2113