-
Bug
-
Resolution: Not a bug
-
Low
-
Minor
-
Issue Summary
Inviting users from the user interface with such emails is working:
имейлНаКирилица@primer and 🎵@primer.com
All the above can be invited from the user interface in Jira Cloud and also can be created in Jira DC.
However when you try to create any by using the REST API:
POST /rest/api/3/user
The server will respond with 500
Steps to Reproduce
try to create user with following emails via rest api "/rest/api/3/user"
имейлНаКирилица@primer and 🎵@primer.com
Expected Results
user created
Actual Results
Response{protocol=http/1.1, code=500, message=Internal Server Error, url=https://.....atlassian.net//rest/api//3//user}
Response Body: {"errorMessages":["The request failed. We're not sure what went wrong. Try again and if the problem persists, contact Jira support."],"errors":{}}
What is expected is to have the same behavior for both UI and REST API or the API to not respond with 500 and have a valid message.
Workaround
Currently there is no known workaround for this behavior (other than creating users via UI).
A workaround will be added here when available
- is duplicated by
-
ACJIRA-2510 Creating user with valid email fails with 500
- Closed
- relates to
-
GORDIAN-942 Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-78003] Creating user with valid email via rest api fails with 500
We had a look at this issue and it seems to be behaving is expected. So closing this issue.
We tried to create these 2 users with following emails via rest api "/rest/api/3/user" and UI
1. имейлНаКирилица@primer
2. 🎵@primer.com
These are both invalid email addresses, so this is not a bug on the apis side as the UI too doesn't allow you to create these users.
This is odd. Using REST API] until Friday (01 April 2022) we were able to create accounts and this weekend suddenly stopped working (same 500 error code and message)... why? 
Looking online for clues I found this open issue, but in our case it was working until recent.
EDIT:
I spoke too quickly before properly checking my directory (managed) accounts. I've noticed that even if the account is pending deletion, a new account with the same email address cannot be created. Thus the generic error. I've just tested it and it worked. No bug for me.
We had a look at this issue and it seems to be behaving is expected. So closing this issue.
We tried to create these 2 users with following emails via rest api "/rest/api/3/user" and UI
1. имейлНаКирилица@primer
2. 🎵@primer.com
These are both invalid email addresses, so this is not a bug on the apis side as the UI too doesn't allow you to create these users.