Versions Compared

Old Version 25

changes.mady.by.user Brandon Bowersox-Johnson

Saved on

compared with

New Version Current

changes.mady.by.user Paweł Gesek

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Bugs

...

Jira Legacy
serverJIRA (openlmis.atlassian.net)
serverId448ba138-230b-3f91-a83e-16e7db1deed1
keyOLMIS-2369

...

Jira Legacy
serverJIRA (openlmis.atlassian.net)
serverId448ba138-230b-3f91-a83e-16e7db1deed1
keyOLMIS-2328

...

Jira Legacy
serverJIRA (openlmis.atlassian.net)
serverId448ba138-230b-3f91-a83e-16e7db1deed1
keyOLMIS-2367

...

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
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2303
     (wasn't picked up for 3.0.2)
    2404
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2268
     (wasn't picked up for 3.0.2)
    2406
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2276
     (wasn't picked up for 3.0.2)
    2355
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-23552408
     New

Critical

  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-23502355
     New
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-22382408
     New
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2329
     (wasn't picked up for 3.0.2)
    2369
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2224
     (wasn't picked up for 3.0.2)
    2414
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-22772382
    - just to clarify, we do not want to allow any duplicates, right?
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-22042350

Major

  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-22952329
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-22752328
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-22432410
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-23062310
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-23522305
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2356
  • still more...

Requisition

...

  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2322
     MUST (request from Malawi)
    2268
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2305
     (UI) (wasn't picked up for 3.0.2)
    2276
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2310
     (UI) (wasn't picked up for 3.0.2)
    2295
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2309
     (UI) (wasn't picked up for 3.0.2)
    2224
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-23512309
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-22392204


  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-1780
    Stretch Goals:
    2164
     (we were not able to see this behvior, needs to be reopened) MUST
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-
    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:
    2241
     MUST
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-
    2321 

...

  • 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
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-

...

  • 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
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-

...

  • 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.

  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2338
    - MUST (blocks OLMIS-2322)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2371
     MUST (SPLIT out OLMIS-22922413 for TeamILL)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2277

Start adding Audit logging for Reference data

  • Users - 
    Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2357
     - MUST

Admin Pages

  • 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 Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2280
     - MUSTView Orderables
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-23702357
     - MUST (Sam is still adding details to story)

...

Jira Legacy
serverJIRA (openlmis.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId448ba138-230b-3f91-a83e-16e7db1deed1
keyOLMIS-

...

2292


Platform

  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-22172232
  • Next on Ad-hoc Reporting (TeamILL)

Stretch:

  • Improve workflow so that fixing bugs results in a new automated test
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2371
    (Malawi doesn't think they'll get to this)
  • Edit Facilities

Platform

  • 1751
     (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
  • Jira Legacy
    Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2232
    Add in design tickets from
    JIRA (openlmis.atlassian.net)
    servercolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2113
  • Next on Ad-hoc Reporting

Stretch:

  • Improve workflow so that fixing bugs results in a new automated test
    2236
    (might need spike)

Team ILL

  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2236
    (might need spike)

...

  • 2379

  • If program data PoC should proceed:

    • Jira Legacy
      serverJIRA (openlmis.atlassian.net)
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-2325
    • Jira Legacy
      serverJIRA (openlmis.atlassian.net)
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId448ba138-230b-3f91-a83e-16e7db1deed1
      keyOLMIS-2324
  • Wait to identify next tickets from
    Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2113