Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

[Eureka ECS] [SPIKE] Request and Item statuses staying in Awaiting pickup status for Secondary request for Items in University tenant

Description

Reproduceable on and only for University tenant

Preconditions:

Request and Item statuses staying in Awaiting pickup status for Secondary request for Items in University tenant

Step to reproduce:

  1. Go to “Requests” app

  2. Scan item placed in University tenant

  3. Scan user

  4. Click on “Save & close” button

  5. Check in Item in University tenant

  6. Check in Item in Central tenant

  7. Check out Item

Actual result: Secondary request: Item status still “Awaiting pickup”, Request status still “Open - Awaiting pickup”

Expected result: Secondary request: Item status changed to “Checked out”, Request status changed to “Closed - Filled

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Checklist

hide

Activity

Show:

Anne Ekblad February 18, 2025 at 3:51 PM
Edited

No development work completed. Solution was to edit the University tenant Loan policy.

Stephanie Buck February 18, 2025 at 1:31 PM

, can the fix be demoed to POs?

Alexander Kurash February 17, 2025 at 4:59 PM

Context

After manual check out in the Central tenant, mod-tlr changes DCB transaction’s status, which triggers mod-dcb to check out an item in the Data tenant (in this case, University).

Results

Check out in the data tenant (University) failed because of University circulation rules:

both policies university-fallback and university-no-loans were not loanable (Loanable: No). After check out failure, item status stayed ‘Awaiting pickup’ (went out of sync with the item status ‘Checked out’ in the Central tenant).

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Vega

RCA Group

TBD

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created February 17, 2025 at 2:58 PM
Updated February 18, 2025 at 3:51 PM
Resolved February 18, 2025 at 3:51 PM
TestRail: Cases
TestRail: Runs