You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When trying to register an Eperson with an already existing email, the save action does not create a new Eperson, but the form submission is performed and user sees three different error notifications.
To Reproduce
Steps to reproduce the behavior:
Login as administrator on dspace7 demo
go to Access Control -> People
click "add Eperson"
fill the form with an email of an already existing user
Expected behavior
Three different notifications might be a bit confusing for the user, we believe he / she should be warned about the already existing email, but with a single error message, or even better, made unable to perform the "save" action if the email is invalid or already in use.
We (4 Science) are available to take in charge this improvement by adding a validator around the eperson creation form that highlights the email input as invalid and preventing form submit action. To add this feature and its test we estimate 4 to 8 hours of effort.
The text was updated successfully, but these errors were encountered:
Describe the bug
When trying to register an Eperson with an already existing email, the save action does not create a new Eperson, but the form submission is performed and user sees three different error notifications.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Three different notifications might be a bit confusing for the user, we believe he / she should be warned about the already existing email, but with a single error message, or even better, made unable to perform the "save" action if the email is invalid or already in use.
We (4 Science) are available to take in charge this improvement by adding a validator around the eperson creation form that highlights the email input as invalid and preventing form submit action. To add this feature and its test we estimate 4 to 8 hours of effort.
The text was updated successfully, but these errors were encountered: