/
Backlog Grooming Sprint 30

Backlog Grooming Sprint 30

Owned by Brandon Bowersox-Johnson
Last updated: Jul 06, 2017 by Paweł Nawrocki (Deactivated)

Goals: Continue building new features in Stock Management and Cold Chain Equipment. Major bugs. Performance. New UI component. 

CCE

Paweł Gesek Could you review the scope for A. Manage CCE Catalog and B. Manage CCE Inventory and let me know if you think it is better for the team to focus on one epic (Catalog) before moving to the next (Inventory).  Or should we first create both domain models?

  • OLMIS-2816 - Getting issue details... STATUS  (MUST)
  • OLMIS-2817 - Getting issue details... STATUS  (MUST)
  • OLMIS-2604 - Getting issue details... STATUS  (MUST) - UI was split into separate tickets
  • OLMIS-2609 - Getting issue details... STATUS  (MUST)

Nice to have

  • OLMIS-2618 - Getting issue details... STATUS  (if we don't want to start on the inventory we could continue to build out catalog tickets)

Q: Paweł Gesek ILL would like to try making showcase videos for the above CCE tickets (OLMIS-2609 & 2618) – please comment if you agree.

Stock Management


Q: Maybe do a showcase video on OLMIS-2711 once it is finished.

Requisition

Fulfillment

  • OLMIS-2795 - Getting issue details... STATUS  (MUST)
  • OLMIS-2724 - Getting issue details... STATUS
  • OLMIS-2726 - Getting issue details... STATUS
  • OLMIS-2781 - Getting issue details... STATUS
    • (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

Reference UI

  • OLMIS-2655 - Getting issue details... STATUS Q: Should we add this to an existing screen? If yes, which one?
  • OLMIS-2661 - Getting issue details... STATUS  (Team ILL)
  • OLMIS-2146 - Getting issue details... STATUS  (Team ILL)
  • OLMIS-2814 - Getting issue details... STATUS  (Team ILL)
  • OLMIS-2030 - Getting issue details... STATUS  (Team ILL)
  • OLMIS-2316 - Getting issue details... STATUS  (TeamILL)
  • OLMIS-2798 - Getting issue details... STATUS
  • OLMIS-2738 - Getting issue details... STATUS  (needs to be reproduced)
  • OLMIS-2714 - Getting issue details... STATUS  (Needs to be reproduced — also needs review to see if general bug and 'global' approach can be taken)
  • OLMIS-2805 - Getting issue details... STATUS
  • OLMIS-2803 - Getting issue details... STATUS
    • 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

Reference Data

Reports

Platform

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)
  • OLMIS-2147 - Getting issue details... STATUS  (Josh Zamor to move to todo after AC check?) (is this or  OLMIS-2611 - Getting issue details... STATUS  a dupe of  OLMIS-1689 - Getting issue details... STATUS  i.e. could we dead the latter)
  • OLMIS-2627 - Getting issue details... STATUS  (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)
  • OLMIS-1329 - Getting issue details... STATUS  (Josh Zamor to check AC)
  • OLMIS-1509 - Getting issue details... STATUS  (Josh Zamor to update AC - ODK developers would find this useful)

OpenLMIS: the global initiative for powerful LMIS software