Versions Compared

Old Version 24

changes.mady.by.user Sam Im

Saved on

compared with

New Version Current

changes.mady.by.user Josh Zamor

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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 are working on 3.1.0 will already have been released around Tuesday, March 28. After that, we will proceed with 3.1.12-SNAPSHOT to do bug fixes, performance, security, & refactoring.

  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2158
     (The approach described in the comments seems correct — as long as the service validates and is the absolute source of information, that all goodalso impacts UI)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-1979
     
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-1780
     (is this worth doing? enough benefit?)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-1391
     (is this worth doing? enough benefit?)

Reference Data

  • (please advise if it impacts UI or other components)


Reference Data

Working toward v5.0.0 - breaking changes in the commodity model endpoints

  • 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?) (Are there any tickers for this?) (Paweł Gesek Yes, please make a ticket for this one if Josh doesn't get to it today. It should be marked Blocker.)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-1695
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-21851696
     (Needs description)


Stretch:

  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-1444
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-16952236





UI

Bugs 

  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-16962219
    ??? Geo data  ??? (MUST)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-1444
    ) Josh to follow up if we need this

UI

...

  • 2137
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2156
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-21262142
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-22032161
     (Q: Which screen are we talking about? Is it administration programs?)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-21032223



New Stuff

  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-21372140
     Must
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-21562242
     Must
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-21422216
     Must
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-21612188
     Must
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2184

...

  • 2267
     Added on 4/3/17 as a MUST
     
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-12712037
     (Should we remove this? Sam has broken out multiple stories for rolesPrioritize sooner for Mary Jo for Malawi)


    These stories have dependencies on each other and must be done in order: 2215, then 2189 and last 2190. (Nikodem Graczewski: Those tickets does not look like they have to be done in order, those are separate screens.)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-21402215
     First
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2216
  • New user setup and administration - Need to talk about workflow with modals (Nick and Sam)
  • ??Other administration screens??
    2189
     Second
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2190
     Third (Q1: Do we want to stick to the modal approach? Wouldn't new screen make more sense in this case? The form is getting quite big. Q2: Are there any Role types on the back-end? Aren't types only related to Rights?)


  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2107
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-1447
     (Nick, I just found this marked fixVersion=3.0.1...moved it to 3.0.2 now, but is it important?)
  • Make ticket for: Designing select all/none – get passed through PC – ILL (repeated below under Team ILL)


  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-20371609
     (Nick to simplify this ticket)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-19252045
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2066


  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-16092164
     (Nick to simplify this ticket)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2165
     

  • Migrate other modals to use OpenLMISModalService (check if has been fixed already)

Stretch Goals

  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2045-1682

Dev-UI

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

Platform

  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2066-1972
     - or 9.6
  • MUST 
    Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-
    2188
  • Migrate other modals to use OpenLMISModalService

...

  • 2250
     (ill)
  • MUST 
    Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-
    1682 

Dev-UI

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

Nick - are 1907 and 1908 a priority? 

...

  • 2251
     (ill)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2233
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2232
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2155
     should this go into the sprint? What component?

...

  • 2180


Service Util

Release 3.0.1.  Next is 3.0.2-SNAPSHOT

  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-1972

...

  • 2155


Notification Service

Stretch:

  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-

...

  • 1751
    (we said we'd pick this up if team tower of power is looking for work - if picked up, this will move Notification service to working on 4.0.0 instead of 3.0.1)

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

Jira Legacy
serverJIRA (openlmis.atlassian.net)
serverId448ba138-230b-3f91-a83e-16e7db1deed1
keyOLMIS-14441853
 (Josh following up)

Jira Legacy
serverJIRA (openlmis.atlassian.net)
serverId448ba138-230b-3f91-a83e-16e7db1deed1
keyOLMIS-2111
 (Might be too big for this sprint)

...

  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2167
    – Need to define the tech persona for this (can they find their IP address and edit a .env file
  • Moved from UI: Make ticket for: Designing select all/none – get passed through PC – ILL

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

  • WARNING 
    Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2113
    – 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)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2166
     (any follow-up needed?)
  • WAIT 
    Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-1997
     (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)
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2162
     or  Assign to Sam 
    Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2160
     or similar? Assign to Sam
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2168
  • Wiki Clean-up: 
    Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2200
     and
    Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2201
     (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)

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

PLUS there are issues marked fixVersion=3.0.2 that were previously 3.0.1 and are not reflected above on this page. Are these important?:

  •  
    Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2232

...

  • -1498
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-1693