ECS | List of requests previously related to bound pieces is displayed in wrong order

Description

Preconditions:

  1. "Allow user to select locations from other affiliations for central orders" option should be not checked (inactive) in "Settings" -> "Consortium manager" -> "Central ordering" in Central tenant

  2. "Ongoing" order associated with organization - "Vendor" from "Preconditions #1" with one PO line exists in "Open" status in member tenant with the following POL settings:

  • "Package" = NOT active

  • "Order format" = P/E mix

  • "Bindery active" = Yes (checked)

  • "Receiving workflow" = Independent order and receipt quantity

  • "Create inventory" = Instance, holdings, item

  1. Two physical pieces were added to related title in "Receiving" app

  2. All pieces have related item in same location (e.g. "Loc 1" in member tenant)

  3. Items related to Piece #1 and Piece #2 have outstanding requests

  • Please note that item should NOT be checked out

  • Each request should have different requester

  1. All created pieces were received

  2. "Set default for receiving search" option is set as "Active affiliation default" in "Settings" -> "Orders" -> "Central ordering" in member tenant

Steps to reproduce:

  1. Go to receiving title details pane in Member tenant

  2. Click “Actions” button in "Received" accordion

  3. Select "Bind piece" option

  4. Fill all mandatory fields, select all pieces, select location from member tenant

  5. Click “Bind” button

  6. Click "Transfer" button

  7. Click on the newly created item record in “Bound items” accordion

  8. Click "2" link in "Request" field

Expected result: List of requests previously related to "Piece #1" and "Piece #2" is displayed in chronological request order (request created first should have the first position in the queue)

Actual result: List of requests previously related to "Piece #1" and "Piece #2" is displayed in wrong order (the last created request has the first position in the queue)

 

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

5

Checklist

hide

Activity

Show:

NinaChistova January 13, 2025 at 9:48 AM
Edited

Tested on bugfest (Okapi and Eureka), works as expected

 

could you please review? Thank you!

Joseph Reimers January 10, 2025 at 6:06 PM

Works as expected

NinaChistova January 10, 2025 at 9:49 AM

Tested on sprint testing https://folio-testing-sprint-cs00000int.ci.folio.org/

Works as expected

 

could you please review? Thank you!

NinaChistova January 9, 2025 at 10:51 AM

Tested on ecs-rancher, works as expected

Waiting for sprint-testing update to verify there

Joseph Reimers January 6, 2025 at 4:03 PM

If we’re including Sprint 207 in Ramsons Bugfix, then that’s the release.

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Thunderjet

Release

Ramsons (R2 2024) Bug Fix

RCA Group

TBD

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created December 23, 2024 at 5:23 PM
Updated January 13, 2025 at 3:39 PM
Resolved January 10, 2025 at 6:06 PM
TestRail: Cases
TestRail: Runs