Backlog Grooming Sprint 37

Goal: Publish a 3.2.1 release candidate by 25 Oct 2017 leading up to a final release hopefully between 1 Nov and 8 Nov 2017. See Release Candidate Process.

The following list is in a flat order:  that is the first thing is first, and the last thing is last.  We start the list with (4) regression tickets, followed by a bug, then a table of ranked performance improvements, and then a few more items which are all lower priority than everything else.  As Team Parrot brings these into their sprint, please keep this order as the order work needs to be prioritized in.

• OLMIS-3291 - Getting issue details... STATUS (MUST) Regression should be a small fix
• OLMIS-3290 - Getting issue details... STATUS  (MUST) Regression should be a small fix
  
  • Q: Should we refactor endpoint to be RESTful? A: Since this is the last sprint, let's leave the endpoint the way it is and not risk breaking.
• OLMIS-3285 - Getting issue details... STATUS regression
• OLMIS-3170 - Getting issue details... STATUS regression
• OLMIS-3246 - Getting issue details... STATUS

performance, in rank order, only displaying un-resolved.  See filter or this screenshot for the rank order that was finalized by ILL as of Oct 11, 2017.

• OLMIS-3295 - Getting issue details... STATUS  Clear and easy fix
• OLMIS-2693 - Getting issue details... STATUS  
• OLMIS-3243 - Getting issue details... STATUS  May need a final requirement call by Rachel Powers (Deactivated). Update: Rachel Powers (Deactivated) added comment to ticket with proposed solution
• OLMIS-3231 - Getting issue details... STATUS  This is minor but feels like we should do CCE right the first time...I could move down if others think it is okay to move forward without it being done.
• OLMIS-3107 - Getting issue details... STATUS  (Team ILL)

Testing

• Regression test ticket for Sprint 37 (Team Parrot)
• OLMIS-3365 - Getting issue details... STATUS  (Sam)

Team ILL

• Lead Ona-OpenSRP/BAO-DHIS2/OpenLMIS summit (agenda here) - 40%
• Employee Evaluations done and FY18 Goals into ReviewSnap by 20th - 5-10%
• Prepare for Release Candidate and Regression Test Cycles
• FYI, Ticket writing will be happening around Re-Supply (Chongsun), and maybe 360-day calendar
• UI Performance follow-through (Perf tickets will come back to Team ILL during QA step) 
• OLMIS-3361 - Getting issue details... STATUS