-
Type:
Bug
-
Resolution: Cannot Reproduce
-
Priority:
Low
-
Component/s: Import/Export - External System Import
-
None
-
1
-
Severity 3 - Minor
Issue Summary
If we delete a user, e.g.: user@gmail.com
, and then try to import this user via JSON, it will return an error that says that the user already exists, because we store the user as a former user.
Steps to Reproduce
- Import a user via JSON using the "External System Import".
{ "users": [ { "name": "1", "fullname": "Chris 2", "active": true, "email": "cristiano1@gmaiil.com", "groups": [ "group" ] }, { "name": "2", "fullname": "Chris 2", "active": true, "email": "cristiano2@gmaiil.com", "groups": [ "group" ] } ] }
- Then, delete this user.
- Next, try to import the user again with the same JSON.
Expected Results
These users were deleted, so Jira should import them again.
Actual Results
The users won't be imported because we have information about this user as a former user. Below, follows the log that will appear.
2021-02-01 15:02:00,640 INFO - Only new items will be imported
......
2021-01-29 19:14:22,869 INFO - 0 users successfully created.
The problem were entries in cwd_user entry in Database, Jira maintains the information as Former Users, like this:
| display_name | email_address | external_id |
|---|---|---|
| Former user | 5cc7016878c01800767577c2 | |
| Former user | 5cc7016b9592cc00762cc8c8 |
Their emails are not in the Database, as we can see above. However, the Atlassian Account ID is still there, so Jira can get these user's email indirectly.
Workaround
Invite the user manually via user management.