2019-07-10 TC Meeting notes

Date

Jul 10, 2019

7am PST / 4pm CEST

Meeting Link

Attendees

@Łukasz Lewczyński (Deactivated)
@Klaudia Pałkowska (Deactivated)
@Aleksandra Ciesińska
@Nikodem Graczewski (Unlicensed)
@Wesley Brown
@Sebastian Brudziński
@Paulina Buzderewicz
@Aleksandra Klasa
@Jakub Jakubowski (Deactivated)
@Josh Zamor (Deactivated)

Discussion items

Time	Item	Who	Notes

Time	Item	Who	Notes
5m	Agenda and action item review	@Josh Zamor (Deactivated)
10m	Review revised mock-ups for orderables/FTAPs screens	@Aleksandra Klasa	Review proposed mock-ups and try to make decisions on implementation
10 m	Updates from last time? Collecting notes on next steps on reporting stack	@Josh Zamor (Deactivated)	We have: Production Readiness 2/2 - https://openlmis.atlassian.net/browse/OLMIS-6182 Data pumps Reduce 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 https://openlmis.atlassian.net/browse/OLMIS-5569 (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 costs	@Sebastian 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 https://confluence.atlassian.com/jirakb/how-to-migrate-projects-from-one-jira-cloud-application-to-another-779160766.html
(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 it
- Malawi 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

Zephyr is $$$$, can we do a homegrown solution to get away from them
Export them to Google Sheets as templates
- export 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

@Sebastian Brudziński to check with Angola team on if all reporting stack improvements have made it into core for next release

@Josh Zamor (Deactivated) to check with @Christine Lenihan on Malawi timeline

@Wesley Brown to followup with @Sam Im (Deactivated) and @Joanna Szymańska (Deactivated) and @Joanna Bebak (Deactivated) on test cases

@Josh Zamor (Deactivated) to followup with @Chongsun Ahn (Unlicensed) on presenting Casper: given timezones could another team member give a technical update (what we're doing, what's working well, what's a trouble spot, etc)