-
Type:
Suggestion
-
Resolution: Duplicate
-
Component/s: Integration - Identity
-
None
Summary
Custom Field User Picker (multiple users) is removing the users that had their usernames changed when you're editing the field.
You can check here a short video about this problem.
Steps to Reproduce
- Create a User: charlie
- Change their user_name to atlassian (customer could have it done themselves prior to the username deprecation). This will cause the user_name to be different from the user_key.
- Create a User Picker (multiple users) custom field and associate it to a project.
- Create an issue, and under the user picker custom field, include atlassian user and save the field using the Old Issue View.
- Click to edit the field and atlassian user will not be displayed and then click on Save icon and the user will be removed from the field.
- Add the atlassian user again.
- Go to the Edit Issue page, the user picker field will not display atlassian user even after you added again.
Expected Results
The users should not be removed from the field while you're editing it.
Actual Results
If you edit a User Picker (multiple users) using the Old Issue View, the users, that had their usernames changed, will be removed from the field. Also, they will not be displayed as a value in the field on the Edit Issue screen.
Workaround
This problem is not happening in the New Issue View, so, in case it's available, you can use it as a workaround.
- is duplicated by
-
JRACLOUD-71865 Custom Field User Picker (multiple users) is removing some users while you're editing the field
-
- Closed
-
- is related to
-
JRACLOUD-71467 Editing the value of user picker custom fields results in an error if the user had their user_name changed.
-
- Closed
-