/
Backlog Grooming Sprint 22

Backlog Grooming Sprint 22

Mar 22, 2017

Priorities

For Sprint 22, our target is to release ref-distro version 3.0.1 by the end of this sprint (sprint ends March 29). This means bugs, performance issues, security issues, adding test coverage, and refactoring. However, we have started to add some additional features. Please make sure component leads are aware and releasing their component as 3.0.1 OR 3.1.0 OR 4.0.0 when necessary. Please take care on breaking API compatibility or functionality! Components can put their release out any time (don't need to wait until the very last day of the sprint). @Josh Zamor (Deactivated) will be helping us establish a process where each component can put out a 3.0.1 release and then switch to working towards 3.1.0-SNAPSHOT.

Goals for ref-distro 3.0.1:

  • UI improvements and finalization (bugs)

  • Finalize requisition data validations 

  • Finish audit logging

Warning!

We need to release during this sprint, so we do not want to start work that might be half-done at the end of the sprint. We cannot leave half-broken things in for the release. Please work in the priority order below, because we've carefully prioritized what is more important for the 3.0.1 release.

 

Questions:

Breaking changes after auth-reference data dependency switch - endpoints have changed:

https://openlmis.atlassian.net/browse/OLMIS-1694

  • /api/users resource stays in referencedata

  • PUT /api/users is only accessible with service level token

  • PUT /api/users/auth is actually used for creating users and sends a request to referencedata to update the profile

We could get around this by:

  • keeping the PUT /users in referencedata and creating oauth users when setting the password in /users/auth/changePassword endpoint

  • adding password to the user in referencedata and implementing custom UserDetailsService in auth service

 

 

Bugs (mostly UI)

UI Features

Administration Screens (needed for ref-distro 3.0.1)

FYI: We will address User Roles and Facilities admin screens in later sprints.

Priorities (in order):

Stretch goals/nice to do—only pick these up after the other MUST sections below are done:

 

Requisition Features

 

Fulfillment Features 

Platform Features

 

To Be Discussed during Q&A Meeting

  • lot management in RefData might become an assignment for Teams AYIC/TOP

Team ILL

Reporting Epic OLMIS-2048 contains: 

@Brandon Bowersox-Johnson to follow up with @Chongsun Ahn (Unlicensed) about if fulfillment should roll the 3.0.1 for fulfillment and then start on feature work.
Make sure all fix versions are 3.0.1

Holding Off

Parking Lot

  • "No concept of store room" or multiple stock locations within one facility (or facility-within-facility model)

  • Start a Glossary area in the wiki (it may be referenced by Configuration Guide later)

Spike Program Data - need tickets to be made and clearly state what the outcome of the spike should be

Performance (sprint 22)

  • Work towards (in-service) caching

 

 

OpenLMIS: the global initiative for powerful LMIS software