/
Backlog Grooming Sprint 20

Backlog Grooming Sprint 20

Owned by Mary Jo Kochendorfer (Deactivated)
Last updated: Feb 16, 2017 by Josh Zamor

Squashing bugs and making the software stable will be very important. Within the UI, there are a couple final features and polish. For platfrom there are some key tickets and tasks we want over the finish line.

Release Accoutrements

  • OLMIS-1921 - Getting issue details... STATUS  Team ILL

  • OLMIS-1922 - Getting issue details... STATUS  Team ILL

Requisitions

Priorities: 1. Bugs. 2. Contract Tests. 3. Tech Debt.

1. Bugs

  • OLMIS-1905 - Getting issue details... STATUS   (Sebastian: many questions in the ticket)
  • OLMIS-1869 - Getting issue details... STATUS   (Sebastian: question in the ticket)

2. Contract Tests 

3. Tech Debt

Decided not to do 1108, 966, or 1391.

Why? It's more important to me to have a stable release, even if it contains this tech debt, rather than try to do these refactors and have the system be unstable on release day.

Fulfillment

  • OLMIS-1915 - Getting issue details... STATUS
  • OLMIS-1916 - Getting issue details... STATUS   (Sebastian: decision how to fix pending in ticket comments)

  • OLMIS-1821 - Getting issue details... STATUS

Auth

NOTHING!

Notification

UI

Bugs should be prioritized however we hope to get through all the tasks as well; Product Grid is the most important feature, and should be worked on first

Tasks in priority order:

  • OLMIS-1920 - Getting issue details... STATUS (Sebastian: question/confirmation in the ticket comment)