-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
6.1.6, 6.3.12
-
6.01
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Steps to reproduce :
- Create a user(lets say 'test') and using the user, perform certain actions on any issue (like adding issue links, comments etc)
- Notice that the issue history tab shows changes made by this user 'test'.
- Now rename this user from administration console giving it a new username (say 'testabc').
- Now make some more changes to the issue using this renamed user.
- Now go to the history tab and notice that the old username 'test' is still being used. The new username 'testabc' is never used in the history tab.
This is expected behaviour looking at the way JIRA has been designed (checking for username field in table 'userhistoryitem' instead of user id). However for a user, this is a bug.
- is duplicated by
-
JRASERVER-68450 Issue history displays user key instead of username for reporter or assignee changes
- Closed
-
JRASERVER-41216 Issue history displays user key instead of username for reporter or assignee changes
- Closed
- relates to
-
JRACLOUD-41203 History tab shows old username after rename of username
- Closed
-
JRASERVER-61871 Improvement to show username instead of user_key in issue's history tab
- Gathering Interest