JIRAUSER## instead of Jira Username in history

[sever6159]

Hello! Noticed that I have [JIRAUSER##] instead of Jira Username in history for new users and get e-mail notifications as from Anonymous for these users. How can I revert to previous settings? Is there any way to change user keys for existing users?

Jira 8.4.1

Thanks in advance

P.S. It's crucial to fix e-mail notifications, user keys aren't so important. I've joined them in one question thinking the root cause is the same. 

[Sagar Mahajan]

Hi @sever6159 and @Stefan Junge This is the intended change from Atlassian after Jira version 8.2 due to the GDPR compliance policy.

More details can be found on below document

https://confluence.atlassian.com/jiracore/gdpr-changes-in-jira-975041009.html

The username and user-key should be same for users were created on a prior Jira release(before 8.2), so you are seeing the difference in the username and user_key for only those users that have been created after upgrading to a higher release.

Updating it through database is tricky as user-key is used in multiple database tables like below

avatar
changegroup
changeitem
clusterlockstatus
component
customfieldvalue
entity_property
favouriteassociations
fileattachment
filtersubscription
jiraaction
jiradraftworkflows
jiraissue
jiraworkflows
os_historystep
portalpage
project
projectroleactor
propertyentry
propertytext
remembermetoken
searchrequest
userassociation
userhistoryitem
worklog

For notifications part does the issue persists for newly created users (users created after version 8.2) or old users are also affected by this?

Generally Jira uses First Name and Last Name of the user for sending the emails, did you see any error in the jira-outgoing-email logs?

[Stefan Junge]

Hi @Sagar Mahajan

thanks for your quick reply. The only effect I can see ist the history tab of an issue. We testet email and it is ok, the name of the user appears correct.

Only newly created users are affected from this situation.

[Sagar Mahajan]

Hi @Stefan Junge Glad to hear that issue with notification is fixed,

Regarding the user-key issue :

Before Jira 8.2 as mentioned in the document

the user key is the same as the username, lowercase. For example, user {{Admin}} will get a user key {{admin}}. If there's a naming conflict, the user key will be set to a value like {{ID10100}}.
Atlassian has change this approach so that all user keys for *new users* (no changes for existing users) have the following format: {{JIRAUSER10100}}

Due to this one of our automation was failing which sync the issues from Bugzilla to Jira from our custom plugin which uses setAssigneeId and setReporterId in the plugin code to copy the values of assignee and reporter from Bugzilla to Jira.

But this is how currently it is configured, so we have to live with it.

[Stefan Junge]

@Sagar Mahajan Many thanks for your eplanation.

[Kishan Sharma]

I think you are affected by this bug and there is a new suggestion as well to show username instead of user_key in Issue History tab.

I would suggest you to cast your vote and start watching both of them for updates and also raise a support ticket to Atlassian to see what they suggest. 

[Stefan Junge]

Hi, here the same issue.

Jira Server 8.13.10.