"Username already exists" error when creating second user with null username

Description

Steps to repro:

  1. Log into folio-testing or folio-snapshot

  2. Go to Users and notice that all the sample user data seems to have Username populated

  3. Username is not a required field, though

  4. Only library staff that use FOLIO need a username and password. Most patrons and users do not

  5. Anyway, create a new user and leave the username and password blank

  6. Saves successfully

  7. Now try again with a second user

Expected: Should save without error. While usernames need to be unique, it should be possible to have more than one null!

Actual: Error and can't save record

Screencast attached.

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

2

Checklist

hide

TestRail: Results

Activity

Show:

Julian Ladisch September 10, 2019 at 12:57 PM

The fix can then been backported to 15.6.1 (= Q3.1 release version) to create 15.6.2 for Chalmers.

Julian Ladisch September 10, 2019 at 12:27 PM

Adam Dickmeiss September 10, 2019 at 10:23 AM

I think I just was the default assignee.. We'll figure out how's best to fix this ASAP

Cate Boerema September 10, 2019 at 9:26 AM

Oh! I see already picked this up (thanks!).

Adam, this might need to be patched to Q3.1 release along with Do you think that would be possible? Chalmers is going live for Circulation on the Q 3.1 release on September 30th. They won't be upgraded to Q3.2 until mid to late October

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Core: Platform

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created September 10, 2019 at 9:20 AM
Updated January 3, 2020 at 2:31 PM
Resolved September 11, 2019 at 8:12 AM
TestRail: Cases
TestRail: Runs