Backlog Grooming Sprint 44

Goal: Fulfillment features and address blocker bugs.

Dates:  -  

6 Sprints left till 3.3 release

Fulfillment

Nikodem Graczewski (Unlicensed) Paweł Gesek Note: At the Sprint Q&A meeting, we would like to hear you describe these tickets and tell us what order you might work on them in. We basically want to see if these tickets make sense. We want to start giving tickets more context/user story understanding. One of our ideas from Retrospective meeting was to ask you to describe the tickets and your proposed order during Q&A meetings as a way to see if the tickets make sense. -Brandon

  • OLMIS-239 - Getting issue details... STATUS  Q: in ticket
  • OLMIS-1611 - Getting issue details... STATUS  (Team Parrot: We have tried to make 1611 a true User Story without giving so many technical implementation details in this ticket. Please review and let us know if you choose to make sub-tasks for the technical details. If there is technical design, please give Team ILL a chance to review. Team ILL would like to hear whether this is helpful to keep tickets high-level.) Q: in ticket
  • OLMIS-3726 - Getting issue details... STATUS  Q: in ticket
  • OLMIS-3818 - Getting issue details... STATUS  
  • OLMIS-3805 - Getting issue details... STATUS
  • OLMIS-529 - Getting issue details... STATUS

Bugs

DISC Visualization Demo Data

  • OLMIS-3874 - Getting issue details... STATUS  Team ILL API design decisions needed
  • OLMIS-3820 - Getting issue details... STATUS

Requisition


Team ILL


OpenLMIS: the global initiative for powerful LMIS software