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.

•  Requisition (Malawi fixed this on their side already)
•  Requisition (MUST)
•  Requisition (MUST)
•  Requisition (MUST)
• 
• 
•  Reference Data
•  Batch Requisition
•  Requisition
• 
•  (Core team to continue looking into and figure out a plan of action)
• 
•  (Nick Reid (Deactivated), needs to be filled out)
• and more.... what are the top priorities?

CCE

F&E

•  (Shall we break this up or not?)

Stock Management

• 
• Ticket for creating more demo data (maybe for Team ILL)

Admin Screens/ Configuration Reporting

Sam Im (Deactivated) are these completely ready for work? Are they in priority order

• 
•  Sam Im (Deactivated) there are still open questions in the ticket.
•  (Team ILL - Sam to work with Chongsun and Josh on questions in this ticket before it can be worked on)

Requisitions

Reference UI

• 
•  (can be fast)
• 

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)

• 
• 
  • Partially completed in 
• 
  • 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 21 Sep 2017 . If bugs come in after that, please make sure to flag prior to 26 Sep 2017 so we can review prior to planning.

Mary Jo pasted the following from sprint 35. Please delete or prioritize.

•  (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)
•  (also identified for the gap analysis) unskipping a period
•  (Did Malawi fork this page? Could the team check the APIs? Malawi will check the APIs)

•  (Not urgent, but perhaps worth mentioning so it isn't forgotten.)