Versions Compared

Old Version 47

changes.mady.by.user Josh Zamor

Saved on

compared with

New Version Current

changes.mady.by.user Paweł Nawrocki

Saved on

Key

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

...

  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-26092816
     (MUST)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2817
     (MUST)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2604
     (MUST) - UI was split into separate tickets
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-27902609
     (needs investigationMUST)

Nice to have

  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2618
     (if we don't want to start on the inventory we could continue to build out catalog tickets)

...

  • Finish all parts of 
    Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2711
     (in current sprint but has lots of sub-tasks)
  • Brandon Bowersox-Johnson to work on next tickets for connecting Req and SM based on Connecting Stock Management and Requisition Services - Team ILL
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2741
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2737
  • Bug to Fix RAML (found by Team Parrot)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2790
     (needs investigation)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2808


Q: Maybe do a showcase video on OLMIS-2711 ?

Requisition

once it is finished.

Requisition

  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2800
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2801
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2715
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2747
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2517
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2797
     (ILL)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)

    Need to set correct behavior – assume field errors only show after user leaves cell (could also show errors as user leaves row, or tries to change page)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2796
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2799

Fulfillment

  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2795
     (MUST)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2724
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2726
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2781
    • (based on discussion in PR #4 — Paweł Gesek has reviewed the issues there and has a suggestion for how we move forward: his suggestion is to remove the GET /api/orders endpoint entirely. This "get all orders" endpoint is not used by the UI or anyone as far as we know. Instead everyone will use the /api/orders/search endpoint to find a specific set of orders returning a list of order UUIDs. Pawel also believes the GET /api/orders is not in v2, it was only created in v3 but never used.  Josh Zamor do you agree?
    • Paweł Gesek, please see latests guidance in OLMIS-2781

...

  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2655
    Q: Should we add this to an existing screen? If yes, which one?
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2661
     (Team ILL)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2146
     (Team ILL)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2814
     (Team ILL)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2030
     (Team ILL)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2316
     (TeamILL)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2798
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2738
     (needs to be reproduced)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2714
     (Needs to be reproduced — also needs review to see if general bug and 'global' approach can be taken)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2805
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2803

    • The remaining work here is centering the modal (and actually all modals)
    • There is a discussion about how center we want these modals to be (generally off center looks right)
    • Ideally the modals would adjust based on the screen height
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyMW-348
     Login needs loading modal (bring in from MW-UI)

Reference Data

  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2716
     (Need additional feedback in comments from Josh Zamor before working on this.)Admin page: 

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

    Jira LegacyserverJIRA (openlmis.atlassian.net)serverId

    448ba138-230b-3f91-a83e-16e7db1deed1keyOLMIS-2541 (Team ILL) - unless ILL can make decision before 7/6
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2787
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2811

...

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

Platform

  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-26682812
    Configuration report: Sam Im - (Deactivated) do you have one that you consider to be the most important? Please schedule a meeting with folks on Thurs or Friday so we can start to address the open questions on Validate Configuration. Open questions are around how we want to implement these.ILL) Josh
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-
    2760

...

  • 2813
    - (ILL) Josh
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2812
     - josh
  • write guidance on testing goals (network, reference data size/caching, tee up selenium) - josh
  • fix pipeline views (only CCE seems to be working)

...

Malawi Contributions

Team ILL and Ben Leibert and Sebastian Brudziński to figure out how to get the following features back into core.

  • Report Service
  • Performance work
  • Batch approval
    • blocked by refactor work in the requisition service
    • UI could be structured as separate service
  • UI - Login page
    • Loading modal ticket
  • UI - Select2
    • MW-268 & MW-274
  • UI - Login Service
    • Configurable currency
    • Cleaner version of clearing user data


Josh Zamor notes. 

  • Add ticket(s) for Next Step on Performance Benchmarking and performance fixes. Can we take the MW team results from OLMIS-2701 and turn it into a wiki page with a standard suite of tests we can periodically benchmark against? Mary Jo created a Non-Functional wiki page where we should clarify our non-functionality performance goals/standards. Also, MW team has specifically identified MW-366 and MW-367 to fix.  (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-2147
     (Josh Zamor to move to todo after AC check?) (is this or 
    Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2611
     a dupe of 
    Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-1689
     i.e. could we dead the latter)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2627
     (Paweł Gesek Please read this ticket and let us know if you think it's feasible and how you would approach it; it would likely need guidance or involvement from you)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-1329
     (Josh Zamor to check AC)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-1509
     (Josh Zamor to update AC - ODK developers would find this useful)Also, we have asked component leads to upgrade Gradle and tooling versions (see https://groups.google.com/forum/#!topic/openlmis-dev/2LpkxEk5vFM). Should we use tickets to track this (so we have a consistent version used before our next release)?