Backlog Grooming Sprint 21
Priorities
For Sprint 21, we will focus on patch work (3.0.1). This means bugs, performance issues, security issues, adding test coverage, and refactoring. We want to first work on things that that do not break API compatibility or break functionality. Our target is to put out a patch release, 3.0.1, by the end of Sprint 22 (late March). After we are done with patch work, Josh will be helping us establish a process where each Component might put out a 3.0.1 patch release and then switch to working towards 3.1.0-SNAPSHOT.
Goals for 3.0.1:
UI improvements and finalization (bugs)
Finalize requisition data validations
Finish audit logging
Improve monitoring
Fulfillment
https://openlmis.atlassian.net/browse/OLMIS-1916 (need to discuss, Sebastian: we didn't put it into the sprint yet, because we don't know how to proceed)
https://openlmis.atlassian.net/browse/OLMIS-1395 (kinda a bug)
UI Bugs
https://openlmis.atlassian.net/browse/OLMIS-1990 (Question from Mateusz in the ticket)
https://openlmis.atlassian.net/browse/OLMIS-2016 (Sebastian: let's agree and include in the ticket description how it is supposed to look after refactor)
https://openlmis.atlassian.net/browse/OLMIS-2000 (Sebastian: let's agree and include in the ticket description how it is supposed to work after refactor)
https://openlmis.atlassian.net/browse/OLMIS-1999 (Sebastian: let's agree and include in the ticket description how it is supposed to look after refactor)
https://openlmis.atlassian.net/browse/OLMIS-1998 (Sebastian: should we have a separate tab for full and non-full supply or just a column that notifies about it?)
Needs to be reproduced
Reference Data Bugs
https://openlmis.atlassian.net/browse/OLMIS-1977 (Sebastian: what response should we have on this "partial success"?)
https://openlmis.atlassian.net/browse/OLMIS-1854 (Josh is this something we should do? - yes)
https://openlmis.atlassian.net/browse/OLMIS-1694 (Sebastian: what's the reason for this change? We assumed that we don't want referencedata to depend on any other services)
Requisition
Bugs first for the patch. Then 1911. I would like to see 1911 completed by end of March.
https://openlmis.atlassian.net/browse/OLMIS-1989 (I (MJ) think this is almost like a bug and could go in the patch. FYI @Brandon Bowersox-Johnson)
Fulfillment Features (do after Bugs)
https://openlmis.atlassian.net/browse/OLMIS-905 (Sebastian: is fulfillment service README a good place to document this?)
Hold off until after 3.0.1 patch:https://openlmis.atlassian.net/browse/OLMIS-1000 (hold off till after the patch)
https://openlmis.atlassian.net/browse/OLMIS-399 (hold off till after the patch)
UI Features (do after Bugs)
*NOTE:* Currently we are working towards UI features for 3.0.1, which we will assume will continue to use the openlmis-requisition-refUI repository. For the UI that will be released in OpenLMIS 3.1, we will be splitting the UI into independent reusable repositories and sections (the work is scoped in https://openlmis.atlassian.net/browse/OLMIS-1920 and https://openlmis.atlassian.net/browse/OLMIS-1025) – the version number for this OpenLMIS-UI will be 4.0. Once this change in repositories is made work on 3.0.1 will stop, or be limited to patches.
It is my hope that Malawi will use the OpenLMIS-UI v4.0 – which should still be compatiable with OpenLMIS 3.0 services - but will use a different structure than what was released in OpenLMIS 3.0.
OpenLMIS 3.0.1 Feature Work
https://openlmis.atlassian.net/browse/OLMIS-1609 (Sebastian: the ticket says we cannot start it yet)
OpenLMIS 3.1 Feature Work
Stretch Goal
Platform Features
https://openlmis.atlassian.net/browse/OLMIS-1733 - Request from @Paweł Gesek (start with ref data to start and then follow up with others - perhaps this can happen after the 3.0.1.. need to discuss)
Audit logging
Monitoring
Signup with New Relic. Can it monitor: http connections and bytes of artifacts in a page load, overall load time, simulate networks (latency, dropped packets, throughput? What can it offer for quick Docker monitoring?
Target a Discussion for sprint 21 (team ILL to come up with approach) : tracking in google analytics? modals, page load times to figure out page load times. perhaps a request identifier across service
Google analytics: move GA tracking code into an environment variable type approach
Admin Screens
Nick mentioned we should look into improving navigation for these screens
@Sam Im (Deactivated), let's add the tickets here to start on user UI
Will address User Roles and Facilities in later sprints.
Reporting
Security
ILL
OLMIS-2048 Epic contains: https://openlmis.atlassian.net/browse/OLMIS-2049 (Team ILL)
https://openlmis.atlassian.net/browse/OLMIS-1997 (Team ILL)
https://openlmis.atlassian.net/browse/OLMIS-2029 (ILL - Nick)
https://openlmis.atlassian.net/browse/OLMIS-2030 (ILL - Nick)
https://openlmis.atlassian.net/browse/OLMIS-2031 (ILL - Nick)
More New Bugs (found by SolDevelo during Sprint 21 should be groomed for fixing in Sprint 22):
https://openlmis.atlassian.net/browse/OLMIS-2054 (UI) (Nick, I added a comment in ticket about how you want to handle this)
https://openlmis.atlassian.net/browse/OLMIS-2056
https://openlmis.atlassian.net/browse/OLMIS-2057 (UI) (Nick, this one needs your input about color issues)
https://openlmis.atlassian.net/browse/OLMIS-2053 (UI)
Holding off:
Spike Program Data - need tickets to be made and clearly state what the outcome of the spike should be
Performance (sprint 22)
Work towards (in-service) caching
OpenLMIS: the global initiative for powerful LMIS software