-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Medium
-
Component/s: Integration - Identity
-
None
-
Severity 2 - Major
Summary
If a user had their user_name changed, Jira will show an error when setting this the user a value of any user picker custom field.
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 custom field and associate it to a project.
- Create an issue, and under the user picker custom field, search for atlassian and set it as the value. Save the field.
- Just edit the field again and try to save it.
Expected Results
The user picker field is successfully saved.
Actual Results
The following error will be displayed: "Could not find usernames: charlie".
In other words, when you edit the field, it parses the user value as user_key instead of their user_name.
Workaround
None.
- relates to
-
JRACLOUD-71853 Workflow post function Update Issue Custom Field value %%CURRENT_USER%% won't work if user has ever been renamed
-
- Closed
-
-
JRACLOUD-71865 Custom Field User Picker (multiple users) is removing some users while you're editing the field
-
- Closed
-
-
JRACLOUD-71418 Permission schemes may show incorrect user if permission is granted to "single user"
-
- Closed
-
-
JRACLOUD-71862 Custom Field User Picker (multiple users) is removing some users while you're editing the field.
- Closed