-
Bug
-
Resolution: Fixed
-
Low
-
None
-
None
Summary
- If a user already exists and you try to create another user with the same email address it fails without showing an error.
- If a user already exists and you try to create another user with the same email address though bulk create, it shows maxResults must be positive error.
Steps to Reproduce
- Create a user on an instance with < 3 users
- Try to create another user with the same email address
Expected Results
An error is thrown saying that email address is already taken.
Actual Results
No error is thrown at all.
If the user is added through bulk create, error maxResults must be positive is shown.
Notes
This is exacerbated by an 'inactive' user that doesn't appear on the list by default.
Suggest the error message to be meaningful, eg : The user already exists
Workaround
Create a user with a different email address or remove the original user.
[ID-6178] Creating a user that already exists via quick add does not throw error
Workflow | Original: reviewflow [ 1133142 ] | New: JAC Bug Workflow v3 [ 3257934 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Description |
Original:
h3. Summary
# If a user already exists and you try to create another user with the same email address it fails without showing an error. # If a user already exists and you try to create another user with the same email address though bulk create, it shows *maxResults must be positive* error. h3. Steps to Reproduce # Create a user on an instance with < 3 users # Try to create another user with the same email address h3. Expected Results An error is thrown saying that email address is already taken. h3. Actual Results No error is thrown at all. If the user is added through bulk create, error *maxResults must be positive* is shown. h3. Notes This is exacerbated by an 'inactive' user that doesn't appear on the list by default. h3.Workaround Create a user with a different email address or remove the original user. |
New:
h3. Summary
# If a user already exists and you try to create another user with the same email address it fails without showing an error. # If a user already exists and you try to create another user with the same email address though bulk create, it shows *maxResults must be positive* error. h3. Steps to Reproduce # Create a user on an instance with < 3 users # Try to create another user with the same email address h3. Expected Results An error is thrown saying that email address is already taken. h3. Actual Results No error is thrown at all. If the user is added through bulk create, error *maxResults must be positive* is shown. h3. Notes This is exacerbated by an 'inactive' user that doesn't appear on the list by default. Suggest the error message to be meaningful, eg : *The user already exists* h3.Workaround Create a user with a different email address or remove the original user. |
Description |
Original:
h3. Summary
# If a user already exists and you try to create another user with the same email address it fails without showing an error. # If a user already exists and you try to create another user with the same email address though bulk create, it shows h3. Steps to Reproduce # Create a user on an instance with < 3 users # Try to create another user with the same email address h3. Expected Results An error is thrown saying that email address is already taken. h3. Actual Results No error is thrown at all. h3. Notes This is exacerbated by an 'inactive' user that doesn't appear on the list by default. h3.Workaround Create a user with a different email address or remove the original user. |
New:
h3. Summary
# If a user already exists and you try to create another user with the same email address it fails without showing an error. # If a user already exists and you try to create another user with the same email address though bulk create, it shows *maxResults must be positive* error. h3. Steps to Reproduce # Create a user on an instance with < 3 users # Try to create another user with the same email address h3. Expected Results An error is thrown saying that email address is already taken. h3. Actual Results No error is thrown at all. If the user is added through bulk create, error *maxResults must be positive* is shown. h3. Notes This is exacerbated by an 'inactive' user that doesn't appear on the list by default. h3.Workaround Create a user with a different email address or remove the original user. |
Description |
Original:
h3. Summary
If a user already exists and you try to create another user with the same email address it fails without showing an error h3. Steps to Reproduce # Create a user on an instance with < 3 users # Try to create another user with the same email address h3. Expected Results An error is thrown saying that email address is already taken. h3. Actual Results No error is thrown at all. h3. Notes This is exacerbated by an 'inactive' user that doesn't appear on the list by default. h3.Workaround Create a user with a different email address or remove the original user. |
New:
h3. Summary
# If a user already exists and you try to create another user with the same email address it fails without showing an error. # If a user already exists and you try to create another user with the same email address though bulk create, it shows h3. Steps to Reproduce # Create a user on an instance with < 3 users # Try to create another user with the same email address h3. Expected Results An error is thrown saying that email address is already taken. h3. Actual Results No error is thrown at all. h3. Notes This is exacerbated by an 'inactive' user that doesn't appear on the list by default. h3.Workaround Create a user with a different email address or remove the original user. |
Link | New: This issue relates to ROTP-3984 [ ROTP-3984 ] |
I have this issue, however the workaround of removing the user doesn't work for me. I cannot see the user in the User Management list.