Done
Details
Assignee
Joseph ReimersJoseph ReimersReporter
NinaChistovaNinaChistovaLabels
Priority
P3Story Points
1Sprint
NoneDevelopment Team
ThunderjetRelease
Ramsons (R2 2024) Bug FixRCA Group
TBDTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Joseph Reimers
Joseph ReimersReporter
NinaChistova
NinaChistovaLabels
Priority
Story Points
1
Sprint
None
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
Preconditions:
"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
"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
Two physical pieces were added to related title in "Receiving" app
All pieces have related item in same location (e.g. "Loc 1" in member tenant)
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
All created pieces were received
"Set default for receiving search" option is set as "Active affiliation default" in "Settings" -> "Orders" -> "Central ordering" in member tenant
Steps to reproduce:
Go to receiving title details pane in Member tenant
Click “Actions” button in "Received" accordion
Select "Bind piece" option
Fill all mandatory fields, select all pieces, select location from member tenant
Click “Bind” button
Click "Transfer" button
Click on the newly created item record in “Bound items” accordion
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)