Sprint 25 is a shorter and we will release 3.0.2 on 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
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 Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-2404
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-2406
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-2355
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-2408
Critical
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-2355
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-2408
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-2369
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-2414
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-2382
- just to clarify, we do not want to allow any duplicates, right?
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-2350
Major
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-2329
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-2328
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-2410
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-2310
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-2305
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-2356
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-2268
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-2276
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-2295
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-2224
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-2309
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-2204
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-2164
(we were not able to see this behvior, needs to be reopened) MUST
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-2241
MUST
Jira Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-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 Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-2322
MUST (request from Malawi) 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 Legacy
server
JIRA (openlmis.atlassian.net)
serverId
448ba138-230b-3f91-a83e-16e7db1deed1
key
OLMIS-2412
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.
- 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.
(Josh Zamor I put this here for you to consider; it got pulled from 3.0.2/sprint 24. Is it a priority for May (maybe while you're in Poland?)? -Brandon