Uploaded image for project: 'FOLIO'
  1. FOLIO
  2. FOLIO-2473

When requester barcode is changed in Users, requests should update accordingly

    XMLWordPrintable

Details

    • Prokopovych - Sprint 129
    • Vega

    Description

      Steps to repro:

      1. log into snapshot
      2. Go to users and find a user
      3. Create a request for that user
      4. Back in users, change the users barcode
      5. Now go back to Requests and look at the users requests

      Expected:

      • In the results list, the requester barcode should be updated to new barcode
      • On request details, the requester barcode should be updated to new barcode

      Actual:

      • Requester barcode not updated in results list
      • Requester barcode not updated on detail record

      TestRail: Results

        Attachments

          Issue Links

            blocks

            Bug - A problem which impairs or prevents the functions of the product. UIREQ-673 "Sort results by barcode" does not sort properly

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIREQ-650 [BE] When inventory data (e.g. barcode, instance title) changes for requested item, request should update accordingly

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

            Bug - A problem which impairs or prevents the functions of the product. CIRC-1139 Request pick up notice not sent to requester when requester's barcode has been changed after request was created

            • 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-1370 Link from Users to Requests Doesn't Work When User Barcode Has Been Changed

            • 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. CHAL-145 Users has 1 open requests, but no requests are displayed for the user in Requests

            • TBD - To be determined
            • Closed

            New Feature - New feature requests UXPROD-2594 After an item has been associated with a Course - Sync item and inventory data

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

            New Feature - New feature requests UXPROD-3399 When Relevant User Record Attributes are Updated, Synchronize Those Updates with the User's Requests Automatically

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

            Page Loading...

            Activity

              People

                Unassigned Unassigned
                cboerema Cate Boerema
                Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases