Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 26 Next »

MJ Note : Discussed releasing another patch release at the end of this sprint as well. This will allow us one more sprint to get in needed extension points, bugs and more admin screens. Please keep this in mind when planning for sprint 23.

Requisition

We expect version 3.1.1 will already have been released around Thursday, March 30. After that, we will proceed with 3.1.2-SNAPSHOT to do bug fixes, performance, security, & refactoring.

  • OLMIS-2158 - Getting issue details... STATUS  (The approach described in the comments seems correct — as long as the service validates and is the absolute source of information, that all good)
  • OLMIS-1979 - Getting issue details... STATUS  
  • OLMIS-1780 - Getting issue details... STATUS  (is this worth doing? enough benefit?)
  • OLMIS-1391 - Getting issue details... STATUS  (is this worth doing? enough benefit?)


Reference Data

  • Lot Management API endpoints (Stock Team Panda needs this ASAP! Josh Zamor We have this wiki page that maps out proposed Lot Management endpoints, but we need your review and we need to turn this into tickets for Teams AYIC/TOP to code as a top priority after 3.0.1 ref-distro release.)
  • Any other bugs or issues Pengfei had with ReferenceData endpoints that need to change for Stock to proceed?
  • OLMIS-2185 - Getting issue details... STATUS
  • OLMIS-1695 - Getting issue details... STATUS
  • OLMIS-1696 - Getting issue details... STATUS


Stretch:

  • OLMIS-2236 - Getting issue details... STATUS
  • OLMIS-1444 - Getting issue details... STATUS Josh to follow up if we need this




UI

Bugs 



New Stuff

  • OLMIS-1271 - Getting issue details... STATUS  (Should we remove this? Sam has broken out multiple stories for roles.)
  • OLMIS-2140 - Getting issue details... STATUS
  • OLMIS-2216 - Getting issue details... STATUS
  • New user setup and administration - Need to talk about workflow with modals (Nick and Sam)
  • ??Other administration screens??
  • OLMIS-2107 - Getting issue details... STATUS
  • OLMIS-2037 - Getting issue details... STATUS  
  • OLMIS-1925 - Getting issue details... STATUS
  • OLMIS-1609 - Getting issue details... STATUS  (Nick to simplify this ticket)
  • OLMIS-2045 - Getting issue details... STATUS
  • OLMIS-2066 - Getting issue details... STATUS
  • OLMIS-2188 - Getting issue details... STATUS
  • Migrate other modals to use OpenLMISModalService

Stretch Goals

Dev-UI

  • Make watch build just files that changed
  • Add Live Reload

Nick - are 1907 and 1908 a priority? 



Platform

  • OLMIS-2155 - Getting issue details... STATUS  should this go into the sprint? What component?

Stretch

Component leads, are any of the following time sensitive or still needed??

OLMIS-1853 - Getting issue details... STATUS  

OLMIS-1444 - Getting issue details... STATUS  (Josh following up)

OLMIS-2111 - Getting issue details... STATUS  (Might be too big for this sprint)

OLMIS-2074 - Getting issue details... STATUS

OLMIS-1707 - Getting issue details... STATUS

OLMIS-1994 - Getting issue details... STATUS  (is this ILL or SolDevelo?) — Josh and Chongsun to talk about)

Team ILL

  • OLMIS-2167 - Getting issue details... STATUS – Need to define the tech persona for this (can they find their IP address and edit a .env file


Grooming call thinks the following isn't needed for patch release, but planning for month of April is needed

  • OLMIS-2113 - Getting issue details... STATUS – Not critical for patch release – Should figure out when we need it by and work backward
     (Team ILL; Brandon is willing to write up/diagram a few options and bring to a group conversation including Team Panda, Josh, Mary Jo)
  • OLMIS-2166 - Getting issue details... STATUS  (any follow-up needed?)
  • OLMIS-1997 - Getting issue details... STATUS  (we explained versioning to Tech Committee and SolDevelo, but we should update the wiki to capture it—especially that the components are semantically versioned, but the ref-distro uses milestone version numbers; and document that we prefer to coordinate working on master towards one common goal, namely the next release, in order to avoid the added effort of branching; Brandon has some paper notes and is willing to write a draft, but I believe it would really be Josh and Tech Committee that would finalize/approve)
  • OLMIS-2162 - Getting issue details... STATUS  or OLMIS-2160 - Getting issue details... STATUS  or similar?
  • OLMIS-2168 - Getting issue details... STATUS
  • Wiki Clean-up:  OLMIS-2200 - Getting issue details... STATUS  and OLMIS-2201 - Getting issue details... STATUS  (and Mary Jo and Tenly have other wiki work it may be helpful to track)
  • Need to discuss with Mary Jo: go back and adjust how OLMIS-1911 is implemented to be more in line with 1.x and 2.x so future migrations will be smoother (Josh and Brandon raised this)
  • OLMIS-2232 - Getting issue details... STATUS

Plus there are lots of good ideas from the Holding Off section at the bottom of Backlog Grooming Sprint 22

  • No labels

OpenLMIS: the global initiative for powerful LMIS software