Skip to end of metadata
Go to start of metadata

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

Critical

  • OLMIS-2355 - Getting issue details... STATUS
  • OLMIS-2408 - Getting issue details... STATUS
  • OLMIS-2369 - Getting issue details... STATUS
  • OLMIS-2414 - Getting issue details... STATUS
  • OLMIS-2382 - Getting issue details... STATUS - just to clarify, we do not want to allow any duplicates, right?
  • OLMIS-2350 - Getting issue details... STATUS

Major

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.

  • OLMIS-2322 - Getting issue details... STATUS  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.
  • OLMIS-2412 - Getting issue details... STATUS  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.

  • OLMIS-2338 - Getting issue details... STATUS - MUST (blocks OLMIS-2322)
  • OLMIS-2371 - Getting issue details... STATUS  MUST (SPLIT out OLMIS-2413 for TeamILL)
  • OLMIS-2370 - Getting issue details... STATUS  - 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.
  • OLMIS-2280 - Getting issue details... STATUS  - MUST
  • OLMIS-2357 - Getting issue details... STATUS  - MUST Q: what about the password reset mentioned in the comments by Chongsun Ahn?

OLMIS-2292 - Getting issue details... STATUS


Platform

  • OLMIS-2232 - Getting issue details... STATUS
  • Next on Ad-hoc Reporting (TeamILL)

Stretch:

  • Improve workflow so that fixing bugs results in a new automated test
  • OLMIS-1751 - Getting issue details... STATUS  (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
  • OLMIS-2236 - Getting issue details... STATUS (might need spike)

Team ILL

  • OLMIS-2379 - Getting issue details... STATUS
  • If program data PoC should proceed:

  • Wait to identify next tickets from OLMIS-2113 - Getting issue details... STATUS
  • No labels