/
Backlog Grooming Sprint 22

Backlog Grooming Sprint 22

Owned by Mary Jo Kochendorfer (Deactivated)
Last updated: Mar 22, 2017 by Brandon Bowersox-Johnson

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 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:

OLMIS-1694 - Getting issue details... STATUS

  • /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)

  • OLMIS-2084 - Getting issue details... STATUS
  • OLMIS-2081 - Getting issue details... STATUS
  • OLMIS-2050 - Getting issue details... STATUS  (Nick to fill out stub) Q: Is there value in this? Is this 3.0.1?
  • OLMIS-2039 - Getting issue details... STATUS
  • OLMIS-2080 - Getting issue details... STATUS
  • OLMIS-2116 - Getting issue details... STATUS  
  • OLMIS-2117 - Getting issue details... STATUS  (reporting bug)
  • OLMIS-2126 - Getting issue details... STATUS
  • OLMIS-2127 - Getting issue details... STATUS

UI Features

Administration Screens (needed for ref-distro 3.0.1)

  • OLMIS-2110 - Getting issue details... STATUS  Must (Nick Reid (Deactivated) revise to "Rename Requisition Template Screen")
  • OLMIS-2009 - Getting issue details... STATUS  Must Q: Breadcrumbs - do we have any patterns for them?
  • OLMIS-2011 - Getting issue details... STATUS  Must
  • OLMIS-2105 - Getting issue details... STATUS  Must
  • OLMIS-2106 - Getting issue details... STATUS  Must Q: Should this appear for edit user as well? Q: question about saving in the ticket?

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

Priorities (in order):

  • OLMIS-2063 - Getting issue details... STATUS  MUST (Q: Should this be a separate directive?)
  • OLMIS-2070 - Getting issue details... STATUS  MUST (Team ILL)
  • OLMIS-2038 - Getting issue details... STATUS  MUST Q: Doesn't this look exactly like select 2? ...
  • OLMIS-2104 - Getting issue details... STATUS  MUST move GA tracking code must follow this approach

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

  • OLMIS-2107 - Getting issue details... STATUS  nice to have
  • OLMIS-1609 - Getting issue details... STATUS  nice to have
  • OLMIS-2045 - Getting issue details... STATUS  nice to have
  • OLMIS-1447 - Getting issue details... STATUS  nice but lower


Requisition Features


Fulfillment Features 

Platform Features

  • OLMIS-1773 - Getting issue details... STATUS  MUST
  • OLMIS-1774 - Getting issue details... STATUS  MUST
  • OLMIS-1776 - Getting issue details... STATUS  MUST
  • OLMIS-2123 - Getting issue details... STATUS  MUST Q: I don't think we have DNS access.


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: 

    • OLMIS-2077 - Getting issue details... STATUS  (ILL)
    • OLMIS-2078 - Getting issue details... STATUS  (ILL) making a big table


Holding Off

  • Create user journey for Requisitions (to help QAs and implementors)
  • OLMIS-1997 - Getting issue details... STATUS
  • Add "componentFixVersion" field to JIRA and document in wiki and notify teams
  • OLMIS-2049 - Getting issue details... STATUS  (Team ILL)
  • Monitoring:
    • Signup with New Relic.  Can it monitor:  http connections and bytes of artifacts in a page load, overall load time, simulate networks (latency, dropped packets, throughput?  What can it offer for quick Docker monitoring?
    • Target a Discussion for sprint 21 (team ILL to come up with approach) : tracking in google analytics? modals, page load times to figure out page load times. perhaps a request identifier across service
  • OLMIS-2113 - Getting issue details... STATUS  (Team ILL)

  • OLMIS-1696 - Getting issue details... STATUS  (Team ILL. Can we do without Josh?)

  • OLMIS-1695 - Getting issue details... STATUS  (Team ILL. Can we do without Josh?)

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
  • OLMIS-1733 - Getting issue details... STATUS  - Request from Paweł Gesek (start with ref data to start and then follow up with others - perhaps this can happen after the 3.0.1.. need to discuss)



OpenLMIS: the global initiative for powerful LMIS software