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
(perhaps we can pick up this sprint?)
(wasn't picked up for 3.0.2)
(wasn't picked up for 3.0.2)
(wasn't picked up for 3.0.2)
New
New
New
(wasn't picked up for 3.0.2)
(wasn't picked up for 3.0.2)
MUST
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.
MUST (request from Malawi)
Stretch Goals:
(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:
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 (blocks OLMIS-2322)
Insert in second half spatial data..
- MUST
- MUST
- MUST
Stretch:
SPLIT ticket into "Update RefData to add spatial data fields" for TeamILL and "Updated PostgreSQL and RDS to support postgis spatial data" for TOP/AYIC
Platform
Add in design tickets from
Next on Ad-hoc Reporting
Stretch:
Improve workflow so that fixing bugs results in a new automated test
(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