Mark Claims Never Checked Out gives Useless Dialog

Bug #1031067 reported by Jason Stephenson on 2012-07-30
This bug affects 2 people
Affects Status Importance Assigned to Milestone

Bug Description

EG Version: master (20120729) + minor customizations
OpenSRF version: 2.1.1
PG Version: 9.1.4

 A dialog "Please inform your help desk or developers of this error:
FIXME -- this case "Missing" is unhandled. This item needs to be routed to
Stacks" comes up when staff mark a copy as claims never checked out by choosing from the Actions for selected items menu in a patron's Items Out pane.

The item then disappears from the account and upon item status check, it
comes up as 'Missing' as it should.

The functionality works, but the unnecessarily extraneous dialog confuses staff.

summary: - Mark Claims Never Checked Out give Useless Dialog
+ Mark Claims Never Checked Out gives Useless Dialog
description: updated
Changed in evergreen:
status: New → Triaged
Kathy Lussier (klussier) wrote :

Just a note that this dialog occurs when the "Claims Never Checked Out: Mark copy as missing" OU setting is enabled.

Changed in evergreen:
status: Triaged → Confirmed
Jeff Davis (jdavis-sitka) wrote :

We are experiencing this bug on Evergreen 2.4.

Jason Stephenson (jstephenson) wrote :
tags: added: pullrequest
Kathy Lussier (klussier) wrote :

Tested this branch on master.

- Claims Never Checked Out: Mark copy as missing OU setting was set to True.
- I marked a checked-out item as Claims Never Checked Out. There were no error messages.
- The status of the item was changed to missing.
- I subsequently checked in the missing item and received the standard alert that is received when checking in a missing item.

Signed-off branch is at;a=shortlog;h=refs/heads/user/kmlussier/lp1031067_missing_never_checked_out

Dan Wells (dbw2) wrote :

Pushed to master, rel_2_4, and rel_2_3. Thanks, all!

Changed in evergreen:
assignee: nobody → Dan Wells (dbw2)
assignee: Dan Wells (dbw2) → nobody
status: Confirmed → Fix Committed
Dan Wells (dbw2) on 2013-11-11
no longer affects: evergreen/2.5
Changed in evergreen:
status: Fix Committed → Fix Released
milestone: none → 2.5.0
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers