...
- · 991: Requisition status checks missing (are status checks
- · 997: ensure requisitions are tied to periods
- · 760: Create a basic requisition (re-opened) - Paweł Gesek do we need to do this if OLMIS-741 is being completed? 760 is a more basic requisition than 741. Also, if 741 is being completed this sprint – do we need to still do the template fields (see above) or are they completed with this… Let’s sync on this after the showcase to make sure I understand where things are with regard to the template/requisition.
Paweł Gesek: OLMIS-760 mentions a few things that have to be done to make the template functional - tie it to creation process, validate hidden fields and improve the initiate endpoint. In OLMIS-741 there is one field mentioned specifically (stock on hand) that currently has no calculation logic. The logic for the other fields in 741 is there, however the process of enforcing usage of template and making sure it is used is missing, and the idea was to do that in OLMIS-760, while OLMIS-741 covers the existing fields. I understand that this is getting confusing - how about merging OLMIS-760 and OLMIS-741 into one story? - Mary Jo Kochendorfer (Deactivated)- Yes, let's merge them. The initial point of the two was to build incrementally. Stock on Hand details are found in OLMIS-838. The idea was the team would first pick up the template stories, then once completed do the 'creation' story.
- · 380: apply adjustment reason to Adjustment quantity - Paweł Gesek – is this one already covered with OLMIS-741?
Paweł Gesek: I believe we just have a "Total Losses / Adjustments" field in the requisition. I don't think we have any of the endpoints that are described in OLMIS-380 nor the calculations, since I don't see any mention about this in OLMIS-741 - Mary Jo Kochendorfer (Deactivated) ok. Let's try to do the template stories prior to the creation story. That way the creation of a requisition is using the template appropriately and the template already has the calculations put into it. Ok?
Order Related stories
- · 829: setup the transfer properties
- · 398: Generate an order (implements what’s missing from 226)
- · 1006: PoD improvements to be finished
...
- 1017: Enable developers to write component tests by setting up test configuration
UI Tickets
- 1024: Create consensus on UI variations and patterns (Nick)
- 1033: Configurable top navigation area (Nick)
- 1040: User's authentication is checked on page load (Nick)