Requisitions (template and improvements)

Bugs

Tickets

OLMIS-924 - Getting issue details... STATUS Question about the formula - why n-1?
OLMIS-887 - Getting issue details... STATUS
OLMIS-218 - Getting issue details... STATUS Confirmation wanted: When skipping a requisition it does not participate in the calculations for next requisitions (eg. beginning balance)
OLMIS-839 - Getting issue details... STATUS Would an endpoint on the backend that retrieves n last requisitions for the given facility, program and schedule make sense? We currently do not have one and it would simplify and speed up UI a lot
OLMIS-1134 - Getting issue details... STATUS
OLMIS-1063 - Getting issue details... STATUS (ILL)
OLMIS-1413 - Getting issue details... STATUS
OLMIS-1503 - Getting issue details... STATUS Needs clean up (blocks 1501/2)

Potentially

Need to add Ticket for capturing dates at each state change → to be displayed on View Requisitions, "approve" and convert to order screens.

Fulfillment

OLMIS-1555 - Getting issue details... STATUS Chongsun Ahn (Unlicensed) will fill out.
OLMIS-1518 - Getting issue details... STATUS Should we check for status here? Eg. the new endpoint won't work for the already transferred orders
OLMIS-1371 - Getting issue details... STATUS (blocked by OLMIS-1512 - Getting issue details... STATUS )
Any other tickets to support 'view orders screen'

New functionality tickets
- New columns
- View/Calculate Total Requisition Cost
- Comments
- Product skipping and adding back previously skipped products
- Vew orders
Tech Debt
- Clean up translation strings. Let's define the end game for this for 3.0 OLMIS-1252 - Getting issue details... STATUS
- Button styleguide
- Sentence documentation (lowest priority and can be moved to next sprint) – Documentation should be written in 30 minutes this sprint

ILL work will be roll over:

OLMIS-1072 - Getting issue details... STATUS OLMIS-1514 - Getting issue details... STATUS

Bugs

Ticket (in priority order)

OLMIS-1084 - Getting issue details... STATUS (blocked by OLMIS-1387 - Getting issue details... STATUS )
OLMIS-1549 - Getting issue details... STATUS (if the APIs are ready) The screenshot shows manage POD screen. This is incorrect, right?
OLMIS-1550 - Getting issue details... STATUS (if the APIs are ready)

Stretch/Sprint 18

OLMIS-1398 - Getting issue details... STATUS
OLMIS-1455 - Getting issue details... STATUS
OLMIS-1556 - Getting issue details... STATUS
OLMIS-1557 - Getting issue details... STATUS
OLMIS-1558 - Getting issue details... STATUS Isn't this done? Also why should we enforce MANAGE_ROLES on rights endpoint?
OLMIS-1563 - Getting issue details... STATUS (Team ILL)
OLMIS-1564 - Getting issue details... STATUS

Reference Data Stretch Goal:

OLMIS-1559 - Getting issue details... STATUS (ILL)
OLMIS-1333 - Getting issue details... STATUS
OLMIS-1449 - Getting issue details... STATUS
OLMIS-1504 - Getting issue details... STATUS
OLMIS-969 - Getting issue details... STATUS The ticket says no classes with ANY dependencies should be moved to shared library. How about classes with Jackson annotations? Eg. some DTOs
Add ticket to capture BI&A calls and effort to finalize the Product Model

Stretch goal (based on TOP/AYIC retrospective):

OLMIS-1606 - Getting issue details... STATUS

OLMIS-1014 - Getting issue details... STATUS Should creating a new user always require an e-mail? Should it be possible for an administrator to set user's password?
OLMIS-1409 - Getting issue details... STATUS