Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-113

Fulfilling delivery requests

    XMLWordPrintable

    Details

    • Template:
    • Potential Workaround:
      Cate Boerema: As far as I know, for institutions that do delivery requests (many), there is no workaround (aside from discontinuing those requests). For this reason, I have increased the rank and labeled po-mvp
    • Epic Link:
    • Analysis Estimate:
      Medium < 5 days
    • Front End Estimate:
      Medium < 5 days
    • Back End Estimate:
      Large < 10 days
    • Confidence factor:
      Medium
    • Estimation Notes and Assumptions:
      assumes simplest case, & similar to Holds
    • Development Team:
      Spitfire
    • Calculated Total Rank:
      85
    • PO Rank:
      96.3
    • PO Ranking Note:
      2019-07-10: As far as I know, for institutions that do delivery requests (many), there is no workaround (aside from discontinuing those requests). For this reason, I have increased the rank and labeled po-mvp.
    • Rank: Chalmers (Impl Aut 2019):
      R5
    • Rank: Chicago (MVP Sum 2020):
      R5
    • Rank: Cornell (Full Sum 2021):
      R1
    • Rank: Duke (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R2
    • Rank: FLO (MVP Sum 2020):
      R1
    • Rank: GBV (MVP Sum 2020):
      R2
    • Rank: hbz (TBD):
      R1
    • Rank: Hungary (MVP End 2020):
      R1
    • Rank: Lehigh (MVP Summer 2020):
      R1
    • Rank: Leipzig (Full TBD):
      R1
    • Rank: TAMU (MVP Jan 2021):
      R5
    • Rank: U of AL (MVP Oct 2020):
      R2

      Description

      Purpose: To implement fulfillment of requests that have a fulfillment preference of Delivery, including:

      1. Settings in User record to determine defaults for fulfillment options
      2. Automatic check out of a requested item to the requester
      3. Alerts at checkin, checkout and renewal that an item is wanted for a request with fulfillment preference "Delivery"
      4. Delivery slips and notices to the patron ("on its way" patron notice may come in separate UXPROD)

      Out of scope:

      • Permission to create delivery request for users who are not normally allowed delivery (this will require action based permissions and, possibly, override functionality) CB: Moved from UXPROD-236

      Mockups for fulfillment preference setting on user record: https://drive.google.com/drive/folders/1lqjdblpO_3wFLYcZdR4jabGCmp0iFsmC

        TestRail: Results

          Attachments

            Issue Links

            is defined by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-508 Implement "Awaiting delivery" and "Open - Awaiting delivery" Item and Request States

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-509 Expiration of Delivery Requests

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-511 Update request whitelist to handle new "Awaiting delivery" status

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. CIRC-542 Some staff slip tokens are missing from POST /circulation/check-in-by-barcode response

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UICHKIN-109 Route for delivery check in modal + delivery slip

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. UICHKIN-146 {{requester.country}} token not populating for delivery request staff slips

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UICIRC-316 View/edit request delivery slip

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UICIRC-319 Tokens for request delivery slip

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UICIRC-320 Request delivery slip preview

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-798 Include New "Open - Awaiting delivery" Status When Accessing Requests from Item Record

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-799 Allow "Awaiting delivery" items to be marked Missing

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIREQ-312 Use user's fulfillment preference to drive request defaults

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIREQ-355 Don't Set Hold Shelf Expiration Date for Delivery Requests

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIREQ-356 Actions on "Open - Awaiting delivery" Requests

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIREQ-357 Add Filter in Requests for New "Open - Awaiting delivry" Status

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIREQ-358 Include New "Open - Awaiting pickup" Status When Accessing Request Queue from Requests Record

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIREQ-359 Update request whitelist to handle new "Awaiting delivery" status

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIREQ-369 Disallow editing Fulfillment preference when Request is in Open - Awaiting delivery or Open - Awaiting pickup

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIREQ-375 Test: Make sure delivery requests work with the Move requests feature

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. UIREQ-380 Wrong delivery address selected when preference = hold shelf and then changed

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UITEN-54 Service point: Print by default for Request delivery slip

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIU-1302 Include New "Open - Awaiting delivery" Status When Accessing Requests from User Record

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            is duplicated by

            New Feature - New feature requests UXPROD-4 Assign Patron default service point for requests and general customer service

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            relates to

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-436 [Spike] Delivery requests: support request preferences of user

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODKBEKBJ-303 BE: Review UXPROD-113

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIEH-779 FE: Review UXPROD-113

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests UXPROD-1561 Allow Request Policy to Control Request Fulfillment Options

            • P4 - lowest priority level, nice-to have things that require future discussion and design
            • Open

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-437 [Spike] Delivery requests: request processing once an item is checked in

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-441 [Spike] Delivery requests: support tokens for delivery slip

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. CIRC-579 Open requests in snapshot with no queue position

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRCSTORE-150 Delivery requests: add new staff slip - "Request delivery" - to reference data

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. UICHKIN-138 Checking in of a canceled delivery request doesn't register a row on UI

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UICHKOUT-563 Include New "Open - Awaiting delivery" Status When Accessing Request Queue from Check Out App

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. UICHKOUT-584 Item barcode not auto-populating when checking out delivery request

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. UIREQ-384 Duplicate not working when have "Requests: View, create"

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. UIREQ-385 Wrong menus showing when duplicating request when not logged in as diku_admin

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. UIREQ-386 Attempting to duplicate request as user appears to fail, creates a request with no position and then breaks duplication for diku_admin

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. UIREQ-387 Creating request as user other than diku_admin results in "page requests not allowed..." message and then creates anyway

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. UIU-1404 Address type displaying as UUID when displayed in User View

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            requires

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-454 Delivery requests: support tokens for delivery slip

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRCSTORE-154 Delivery requests: Store request preferences of user

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. UIREQ-377 Strange behavior when editing request for item with no barcode

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

              Activity

                People

                Assignee:
                cboerema Cate Boerema
                Reporter:
                cboerema Cate Boerema
                Analysis Estimator:
                Tania Fersenheim Tania Fersenheim
                Front End Estimator:
                Matt Connolly Matt Connolly
                Back End Estimator:
                Marc Johnson Marc Johnson
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases