/
Backlog Grooming Sprint 17

Backlog Grooming Sprint 17

Owned by Mary Jo Kochendorfer (Deactivated)
Last updated: Jan 09, 2017

Themes:

  • Requisitions - keep moving forward with new columns
  • Fulfillment - APIs to support the 'view orders' and 'manage POD' screens
  • Reference data - errors and enforcing rights
  • UI - see the UI section


Rollover Team ILL

Requisitions (template and improvements)

Bugs

Tickets

  • OLMIS-924 - Getting issue details... STATUS Question about the formula - why n-1? Answer: addressed, should be n.
  • 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'

UI


  • New functionality tickets
    • New columns
    • View/Calculate Total Requisition Cost
    • Comment