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

Title Level Requests Complete (part 2)

    XMLWordPrintable

Details

    • Morning Glory (R2 2022)
    • Large < 10 days
    • 80%
    • Out of scope
    • Vega
    • 0
    • R2

    Description

      Current situation or problem:  ** To complete stories and functionality from Title level requests complete feature (part 1) UXPROD-1796

      In scope: Front and backend (if needed) work to complete and/or add functionality in UXPROD-1796

      Links to additional info: 
      Mockups folder: https://drive.google.com/drive/u/1/folders/1ndvI2IIzp6avYbCu1B_YueoZVlGfeuOB
      GDrive folder: https://drive.google.com/drive/u/1/folders/1ao5l4aKi-aNLlXwzT5CJ-UCXaba5tEKE
      Vega documentation folder: https://drive.google.com/drive/u/0/folders/1R8mESODVM_Yt-Od8w6YCv2fe3YbI90R2 

      Refinements:

      Notes:

      • As of 9/10/21, title look-up (on the new Request form) is out of scope for the first implementation of this feature.  
      • As of 9/14/21 it is confirmed that Vega will integrate this work with Inventory only, NOT Inventory ES.
      • All patrons can place title level requests regardless of whether they can be filled or not in the first implementation. Ideally in another implementation we will find a way of controlling who can place TLR request, potentially by excluding patron groups, working with existing circulation rules, extending circulation rules to work with instance data (patron, loan type, material type and location IDs in a list - see if a request can occur)
      • Multivolume series requests will be investigated in a future implementation 

      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-1475 Rebalance title level request recall queue

            • 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. CIRC-1479 TLR not respecting request policies

            • 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-1500 Page request logic should include pickup location when more than one item is available

            • 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-1531 Move TLR to another item

            • 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-1533 Create service for location tree traversal

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRCSTORE-328 Create a timer for TLR feature toggle jobs

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRCSTORE-329 Implement TLR feature toggle job service

            • 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-341 Implement error handling for TLR feature toggle job

            • TBD - To be determined
            • Closed

            Task - A task that needs to be done. FAT-1500 Refinement UXPROD-3392

            • TBD - To be determined
            • Closed

            Tech Debt - FAT-1715 Karate test case C350540: Recall an Item by Placing a Title-level Request Using Patron Services (MOD-PATRON): Item checked out with rolling due date

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIREQ-722 Add success toast to Requests

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIREQ-728 Move page requests to first accordion of unified queue when reordering

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

            Task - A task that needs to be done. UIREQ-740 Spike: Investigate possible for adding toast to requests page create/edit/duplicate and requests page details

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIREQ-747 Add success toast to duplicated Requests

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIREQ-748 Add policy-based error to Requests toast

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIREQ-753 Suppress missing name "undefined" in success toasts

            • 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-757 Ensure Request details # (# requests) shows correct data

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIREQ-767 TLR: Add Move request to Action list when item is attached to title level request for fulfillment

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

            New Feature - New feature requests UXPROD-1796 Title Level Requests Complete (part 1)

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

            New Feature - New feature requests UXPROD-3402 Title look-up for Requests (title level requests)

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

            Activity

              People

                stephaniesbuck Stephanie Buck
                stephaniesbuck Stephanie Buck
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases