Backlog Grooming Sprint 26
Last sprint before 3.1 release. Key features to be demonstrated are related to stock management workflows (conduct a physical inventory, make an adjustment, record an issue/receive), tracking lots and new administration screens. The following tickets are focusing on addressing bugs and stabalizing the requisition service.
Reference UI
Goals: Consistency
Needs Design Work (Expect implementation tickets to fall out of these tickets, not sure if they will make it to 3.1)
- - OLMIS-1354Getting issue details... STATUS (Team ILL)
- - OLMIS-2499Getting issue details... STATUS (Team ILL)
- - OLMIS-2445Getting issue details... STATUS MUST
- - OLMIS-2428Getting issue details... STATUS and - OLMIS-2275Getting issue details... STATUS MUST
- - OLMIS-2471Getting issue details... STATUS MUST
- - OLMIS-2444Getting issue details... STATUS
- - OLMIS-1889Getting issue details... STATUS
- - OLMIS-1693Getting issue details... STATUS (Team ILL)
- - OLMIS-2224Getting issue details... STATUS (Team ILL) In progress
Stretch Goal:
Requisition
Will be working towards 3.1.3-SNAPSHOT. Because requisition-3.1.2 was released in ref-distro-3.0.2.
- - OLMIS-2466Getting issue details... STATUS MUST
- - OLMIS-2481Getting issue details... STATUS MUST
- - OLMIS-2482Getting issue details... STATUS MUST
- - OLMIS-2439Getting issue details... STATUS MUST
- - OLMIS-2453Getting issue details... STATUS MUST
- - OLMIS-2491Getting issue details... STATUS Try to reproduce
- - OLMIS-2480Getting issue details... STATUS Try to reproduce
- - OLMIS-2483Getting issue details... STATUS MUST
- - OLMIS-2436Getting issue details... STATUS MUST
- - OLMIS-2352Getting issue details... STATUS MUST
- - OLMIS-2351Getting issue details... STATUS (very small)
- - OLMIS-2239Getting issue details... STATUS
Stretch Goal:
Reference Data
Will be working towards 5.1.0-SNAPSHOT. Because referencedata-5.0.0 is planned to be released in ref-distro-3.0.2. Improvements such as 2357 make this a Minor bump to 5.1.0, not a patch 5.0.1. Reference Data is working on 6.0.0 due to final changes to accomplish OLMIS-1696.
- - OLMIS-2370Getting issue details... STATUS MUST
- - OLMIS-2371Getting issue details... STATUS MUST(is split out by - OLMIS-2413Getting issue details... STATUS )
- - OLMIS-2357Getting issue details... STATUS MUST
- - OLMIS-2238Getting issue details... STATUS
- - OLMIS-2492Getting issue details... STATUS
- - OLMIS-2489Getting issue details... STATUS
- - OLMIS-2411Getting issue details... STATUS
- - OLMIS-2386Getting issue details... STATUS
- - OLMIS-2292Getting issue details... STATUS
- - OLMIS-2392Getting issue details... STATUS
- - OLMIS-2277Getting issue details... STATUS
- - OLMIS-2494Getting issue details... STATUS
- - OLMIS-2493Getting issue details... STATUS
- - OLMIS-2495Getting issue details... STATUS
Stretch
Fulfillment
- - OLMIS-2484Getting issue details... STATUS (needs to be reproduced) MUST
- - OLMIS-2488Getting issue details... STATUS MUST
- - OLMIS-2243Getting issue details... STATUS (Should be checked to see if still issue) MUST
Platform
Reporting
Team ILL
Discuss how we will keep these moving forward:
- - OLMIS-2113Getting issue details... STATUS
- - OLMIS-2323Getting issue details... STATUS
Should Program Data PoC proceed without Chongsun?Should ad-hoc Reporting proceed?Improve workflow so that fixing bugs results in a new automated test- - OLMIS-1751Getting issue details... STATUS (Josh Zamor perhaps the design of this is a topic to discuss while you are in Gdynia?)
- - OLMIS-2236Getting issue details... STATUS
OpenLMIS: the global initiative for powerful LMIS software