Goal: Squash bugs for the 3.2.1 release. Judiciously continue with F&E features and performance improvements.
Grooming Question: There have been discussions around modifying the release process this time. I'd like to make sure we are clearly communicating the plan to the team. Brandon Bowersox-Johnson do you have an update from the conversations with Josh Zamor?
UPDATE: No decisions yet about the 'release candidate' process or doing a 'slow down and go careful' release for 3.2.1. So for now we are grooming priorities on this page for a squash-bug-and-release scenario, but that could change before sprint 36 begins.
Issue: Malawi faces time-outs when configurations are incorrect. Is there a way to provide an error versus timing out? See the recent slack exchange here
BUGS
There are a lot of bugs. I'm still reviewing and prioritizing. Please let me know which are top priority for you and what the impact of the bug is.
- - OLMIS-3151Getting issue details... STATUS Requisition (Malawi fixed this on their side already)
- - OLMIS-3148Getting issue details... STATUS Requisition (MUST)
- - OLMIS-3213Getting issue details... STATUS Requisition (MUST)
- - OLMIS-3170Getting issue details... STATUS Requisition (MUST)
- - OLMIS-3076Getting issue details... STATUS
- - OLMIS-3144Getting issue details... STATUS
- - OLMIS-3167Getting issue details... STATUS Reference Data
- - OLMIS-3126Getting issue details... STATUS Batch Requisition
- - OLMIS-3215Getting issue details... STATUS Requisition
- - OLMIS-3201Getting issue details... STATUS
- - OLMIS-3137Getting issue details... STATUS (Core team to continue looking into and figure out a plan of action)
- - OLMIS-3140Getting issue details... STATUS
- - OLMIS-3108Getting issue details... STATUS (Nick Reid (Deactivated), needs to be filled out)
- and more.... what are the top priorities?
CCE
- OLMIS-3197Getting issue details... STATUS
F&E
Stock Management
Admin Screens/ Configuration Reporting
Sam Im (Deactivated) are these completely ready for work? Are they in priority order
- - OLMIS-2758Getting issue details... STATUS
- - OLMIS-2217Getting issue details... STATUS Sam Im (Deactivated) there are still open questions in the ticket.
- - OLMIS-2697Getting issue details... STATUS (Team ILL - Sam to work with Chongsun and Josh on questions in this ticket before it can be worked on)
Requisitions
Reference UI
- - OLMIS-3161Getting issue details... STATUS (this could be fast)
- - OLMIS-3195Getting issue details... STATUS
- - OLMIS-2443Getting issue details... STATUS
- - OLMIS-3260Getting issue details... STATUS
Low Priority
Malawi-UI
Nick Reid (Deactivated) is this really something we should be taking on prior to a release?
Goal here is to un-fork MW-UI files to make upgrading possible (and establish extension patterns)
- - MW-419Getting issue details... STATUS
- - MW-437Getting issue details... STATUS
-
-
MW-511Getting issue details...
STATUS
- Fix is related to work in OLMIS-2956
Requests from Malawi
Ben Leibert and Christine Lenihan, please make sure the following tickets are in priority order so that we can review for the next backlog grooming call on . If bugs come in after that, please make sure to flag prior to so we can review prior to planning.
Mary Jo pasted the following from sprint 35. Please delete or prioritize.
- - OLMIS-3147Getting issue details... STATUS (MJ/Ben to speak with Malawi team to see if we can get more information on the desired state or willingness to use workarounds like send emails to spam)
- - MALAWISUP-128Getting issue details... STATUS (also identified for the gap analysis) unskipping a period
- - OLMIS-3157Getting issue details... STATUS (Did Malawi fork this page? Could the team check the APIs? Malawi will check the APIs)
- OLMIS-2829Getting issue details... STATUS (Not urgent, but perhaps worth mentioning so it isn't forgotten.)