No result found search for patron by database id results in return to wrong interface

Bug #978040 reported by Michael Peters
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Won't Fix
Low
Unassigned

Bug Description

Tested in 2.2 Beta 2, but present in master as well.

If you attempt a "Retrieve Patron via Database ID", you receive an ACTOR_USER_NOT_FOUND, which is correct. The problem, however, is that you are then returned to the "Retrieve patron by Barcode" interface, instead of being given another chance at entering the DB id.

This can lead to confusion, if you attempt to re-enter a database ID into this field.

Changed in evergreen:
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Galen Charlton (gmc) wrote :

Still happening in 2.3.4. Marking bitesize

tags: added: bitesize
Revision history for this message
Michael Peters (mrpeters) wrote :

Not relevant since XUL staff client will be soon deprecated. This problem does not occur in the web staff client because search by actor.usr.id value is not present, and really, is not practical since it is very unlikely that staff will know the database ID for a patron on a regular basis.

Changed in evergreen:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.