Loading a staged user can result in a UUID username

Bug #1246859 reported by Jeff Godin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Medium
Unassigned
2.5
Fix Released
Medium
Unassigned
2.6
Fix Released
Undecided
Unassigned

Bug Description

When loading a staged user in the user editor, if the staged user's username is a UUID, the form field is set to that UUID value. It is unlikely that we would ever want to actually create a user with a UUID value for a username.

When creating the user, staff currently need to take manual steps to remove the UUID value and replace it with either a barcode by default or some other manual value.

This is partially mitigated by the following commit related to bug 1207396, which allows staged users to have a non-UUID username:
* 4a3a719 - LP1207396 user stage allows username selection

It would be good to eliminate the UUID altogether, falling back to the staged barcode (if there is a staged card) or a blank value which will populate when staff enter a barcode.

This will bring some consistency to the user creation process, whether the patron is new, cloned, or staged.

Working branch to follow.

Revision history for this message
Jeff Godin (jgodin) wrote :
Changed in evergreen:
milestone: none → 2.5.2
status: New → In Progress
importance: Undecided → Medium
assignee: Jeff Godin (jgodin) → nobody
Jeff Godin (jgodin)
tags: added: pullrequest
Dan Wells (dbw2)
Changed in evergreen:
milestone: 2.5.2 → 2.6.0-alpha1
status: In Progress → Confirmed
Dan Wells (dbw2)
Changed in evergreen:
milestone: 2.6.0-alpha1 → 2.6.0-beta1
Dan Wells (dbw2)
Changed in evergreen:
milestone: 2.6.0-beta1 → 2.6.0-rc1
Changed in evergreen:
milestone: 2.6.0-rc1 → 2.next
no longer affects: evergreen/2.4
Revision history for this message
Ben Shum (bshum) wrote :

Pushed to master and backported to rel_2_6 and rel_2_5. Thanks Jeff!

Changed in evergreen:
milestone: 2.next → 2.7.0
status: Confirmed → Fix Committed
Changed in evergreen:
status: Fix Committed → Fix Released
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.