Backlog Grooming Sprint 24

Owned by Mary Jo Kochendorfer (Deactivated)
Last updated: Apr 14, 2017 by Ben Leibert
3 min read

At the end of this sprint, March 26, we will release 3.0.2 patch. Please keep this in mind when picking up tickets. We want to address key bugs and make minor enhancements. 

  • Add tickets for each component for rolling the release

Requisition

Working on 3.1.2-SNAPSHOT

  • Release 3.1.2 by the end of sprint 24 (and move us forward to 3.1.3-SNAPSHOT). Paweł Gesek should we make a ticket for releasing each component?
  • OLMIS-2288 - Getting issue details... STATUS  (This may be a UI bug, but needs to be diagnosed. This is a bad bug-MUST fix for 3.0.2.)
  • OLMIS-2302 - Getting issue details... STATUS  (UI and API) MUST
  • OLMIS-2314 - Getting issue details... STATUS  MUST
  • OLMIS-2289 - Getting issue details... STATUS  MUST
  • OLMIS-2330 - Getting issue details... STATUS  MUST (updates to Reporting Rate) - sentence in the description cuts off
  • OLMIS-2321 - Getting issue details... STATUS  (Josh Zamor I think we should consider starting on this so we have enough back-end, Java work this sprint. But the ticket has some thorny open technical questions.) Team ILL Discussion: Let's start with a Tech Committee discussion now about the requirements and the design of this extension point. Then coding could begin in Sprint 25. Sebastian Brudziński FYI.
  • Stretch goal:  OLMIS-2239 - Getting issue details... STATUS

Reference Data

Working on 5.0.0

UI 

Working on different versions component-by-component (need to coordinate for this sprint?). We need to put in the different versions for all the UI components

Nikodem Graczewski (Unlicensed), since Nick is out of town. Please let me know if we should be adding other tickets to this next sprint to continue moving towards the goals he laid out in UI/UX Overview + Backlog.

Bugs (Many came from the test done on 4/7 Product Grid Testing)

OLMIS-2307 - Getting issue details... STATUS  - needs clarification

Paweł Gesek I've ranked the bugs by priority in the backlog view. I haven't had a chance to update the wiki with a list of tickets, please pick bugs from the top of this list. They are marked with 3.0.2

Admin screens / Reference Data

Facility Management (please review the wiki page for context and mockups)

These tickets are marked as must, but are not listed for 3.0.2 - are they musts?

  • OLMIS-2284 - Getting issue details... STATUS  MUST - do we want to paginate facilities on the backend?

User Roles (please review the wiki page for context and mockups)

  • OLMIS-2281 - Getting issue details... STATUS  MUST - BUT we need to discuss this in further detail
  • OLMIS-2280 - Getting issue details... STATUS MUST - do we want to paginate facilities on the backend?
  • OLMIS-2282 - Getting issue details... STATUS

General

  • Release UI (RefUI plus any UI components we need to release) (Paweł Gesek same question as above)
  • OLMIS-2164 - Getting issue details... STATUS  MUST
  • OLMIS-2165 - Getting issue details... STATUS  MUST
  • OLMIS-1447 - Getting issue details... STATUS  
  • OLMIS-1189 - Getting issue details... STATUS

Platform

  • OLMIS-2337 - Getting issue details... STATUS  MUST
  • OLMIS-2232 - Getting issue details... STATUS  We don't believe this needs to be done right now given the number of bugs. SolDevelo please let us know if you think is priority for this sprint.
  • OLMIS-2180 - Getting issue details... STATUS  This isn't a high priority.

  • OLMIS-2336 - Getting issue details... STATUS  MUST Team ILL
  • OLMIS-2323 - Getting issue details... STATUS  Team ILL
  • next on routine reports (ill) MUST (rollover OLMIS-2251, work may be done by Malawi in MW-74)
  • next on ad-hoc reports (ill) MUST (roll over)

Auth

Working on 4.0.0

  • release 4.0.0 - work has already been done requiring this change (Paweł Gesek Similar to above, do you want to make a ticket for each component that you will release?)


Stretch:

  • OLMIS-2111 - Getting issue details... STATUS
  • write tickets for making auth endpoints restful and cleaner (would like to pick up to fit these changes in 4.0.0 major version)

Notification Service

Working on 4.0.0

  • release 4.0.0 if and only if the ticket below is completed (otherwise there is nothing to release)


Stretch:

Team ILL

  • Coming to Tech Committee for discussion (see comments): How are we going to address that every time we add ExtraData to any entity, that change breaks our APIs? (Should we hurry and add ExtraData to every entity now? Or can we find a new way to add ExtraData that is backwards-compatible?) Chongsun Ahn (Unlicensed) do you know?

New Work

Rollover


Potential

  • OLMIS-2167 - Getting issue details... STATUS – Need to define the tech persona for this, this is for VR staff like Olivier and field staff (can they find their IP address and edit a .env file)
  • 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)

Plus there are lots of good ideas from the bottom of Backlog Grooming Sprint 23 and earlier


OpenLMIS: the global initiative for powerful LMIS software