Details
-
Bug
-
Resolution: Fixed
-
Highest
-
6.3.14, 7.0.11, 7.1.10, 7.4.6, 7.5.4, 7.3.9, 7.9.2, 7.7.4, 7.8.4, 7.2.15, 7.10.2, 7.11.2, 7.6.9, 7.12.2, 7.12.3, 8.1.1, 8.5.2, 8.6.1, 8.16.0
-
6.03
-
48
-
Severity 3 - Minor
-
290
-
Description
When viewing a Jira issue, the History tab records changes in assignee/reporter using app_user.user_key. This is the only place in the UI where this identifier, normally used only internally in Jira, is used. This should be app_user.lower_user_name to maintain consistency with other UI elements. Raising as a bug as this has GDPR implications; even after anonymizing usernames personal information could be leaked to the UI as user_key is an immutable value.
Steps to Replicate
- Create a user (e.g. jsmith).
- Change its username (e.g. to john.smith)
- Go to any issue and select john.smith as either the assignee or the reporter.
- Click on the History tab.
- The change will display the username jsmith instead of john.smith:
Expected Result
Since the user key is only used internally by the application, we should not expose this information to end-users. The current username should be displayed instead (john.smith).
Additional information about the user rename feature:
https://developer.atlassian.com/display/JIRADEV/Renamable+Users+in+JIRA+6.0
Attachments
Issue Links
- causes
-
-
- Closed
-
- duplicates
-
-
- Closed
-
- is cloned from
-
-
- Closed
-
- is related to
-
-
- Gathering Impact
-
-
JRASERVER-61871 Improvement to show username instead of user_key in issue's history tab
- Gathering Interest
- relates to
-
-
- Closed
-
-
- Gathering Interest
-
BJBR-23 Loading...
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-