Date 10 Jul 2019
7am PST / 4pm CEST
Meeting Link https://zoom.us/j/994971678
Attendees
Discussion items Time Item Who Notes 5m Agenda and action item review Josh Zamor
10m Review revised mock-ups for orderables/FTAPs screens Aleksandra Klasa (Deactivated) Review proposed mock-ups and try to make decisions on implementation 10 m
Updates from last time? Collecting notes on next steps on reporting stackJosh Zamor We have:
Production Readiness 2/2 - Data pumpsReduce brittleness Streamline how data moves How could we apply the strangler pattern to move incrementally to a different approach
Can we focus everything into production readiness #2 epic?
5m Approach to (fulfillment service references Stock Mgmt demo data) Aleksandra Ciesińska / Sebastian Brudziński Follow the same approach as requisition service? 10m Updates from last time? Orderable versioning (fulfillment)Klaudia Pałkowska (Deactivated) Design of Order, Shipment, PoD line item use of Orderable versioning Incrementing orderable version Updates from last time? Reducing Jira costsSebastian Brudziński / Wesley Brown Anything we can do to cut on costs? Especially addon-wise. What are all our users? ~200 active accounts Possibly have two separate Jira instances? One dedicated only to development, that would have Zephyr and other needed apps installed (next time) Look at streaming from Casper
Notes
Review revised mock-ups for orderables/FTAPs screens Looked at two options On second option we felt it fit style guide more, though it might have more user client action involved We're ready to start development on second option!
Reporting Stack updates
Not a focus atm for 3.7 In part as implementations have it, or aren't currently pressed to do it: Angola has itMalawi is rolling it out (or part), perhaps ask Christine Lenihan Angola has a number of fixes, most are likely in core for next release. Could catch up with that team to double check.
Approach to OLMIS-5569
Approach is used in Requisition service Concern that we'll have to maintain it forever
Orderable versioning
Tickets created, but not yet started work in Fulfillment
Jira Costs
Export them to Google Sheets as templatesexport would be 100s of test cases with some having 50-60 steps would lose history of test cycles would be harder to link tickets to steps in test cycles During testing we'd take those google sheet templates, dupe them for the test cycle, and fill them in. We'd get better feedback from Sam Im (Deactivated) or Joanna Szymańska (Deactivated) or Joanna Bebak (Deactivated) how much longer would it take to execute a test case? how much longer to write one? Next step:Investigate if Zephyr can export well into a CSV or otherwise
Action Items