Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


AD user in Jira has strange userkey JIRAUSER46614



Our Jira SD (v4.4.2) users are synchronized from Active Directory. For most of them key, name and username values are the same. For example: 

jira.user=cccccc(cccccc) key=cccccc name=cccccc usrName=cccccc dispName=CCCC DDDD

But some of them have a weird key:

jira.user=aaaaaa(JIRAUSER46614) key=JIRAUSER46614 name=aaaaaa usrName=aaaaaa dispName=AAAA BBBBB

What does it mean? Is this an synchronization issue?


1 answer

1 accepted

0 votes
Answer accepted
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 03, 2020

Hi Salvijus,

I understand that you have several users within Jira whose userkeys match their usernames, but some more recently created users have what appear to be completely random userkeys.  This is not a bug, nor is this a synchronization issue.

Instead this is a change that was made to Jira 8.2 (and Jira Service Desk 4.2) versions and higher in response to GDPR changes in Jira. All versions of Jira server 6.0 and higher have userkeys values for all users.  Historically this userkey value was made to match the username when the account was first created.  Starting in Jira 6 user accounts could be renamed, hence the need of the userkey field in order to keep historical tracking accurate.

However any newly created users in Jira 8.2 or higher will instead use this different format for their userkey when their account is first created.  From that document:

We’re changing this approach so that all user keys for new users (no changes for existing users) have the following format: JIRAUSER10100.

I hope this helps to explain the change in behavior here.


Hi Andy,

Absolutely :)


Like Andy Heinzer likes this

Hello @Andy Heinzer ,

Is there any way to go back to the previous user keys format in JIRA 8?

Any dark feature for example?

It triggers a lot of issue in our organization currently as we just migrated to JIRA8 couple of month ago and the first new users start to appear with the JIRAUSERXXXXX format.

Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jul 30, 2021

Yes, technically there is a dark feature for that.  If you go to <Jira_URL>/secure/SiteDarkFeatures!default .jspa 

You can set the property called


and in turn any new accounts created in Jira after this dark feature is set would be created with the userkey being set to the first username of that account.  Just be aware that this will not change the user_key for any existing account, this only affects newly created accounts.

Should you need to anonymize old user data in the future, then you might want to review Anonymizing users as Jira 8 has added some in product features to help here.


Like JAUTEE Nicolas likes this

Anonymizing is usefull for internal users isn't it ? It is not working on external users ?

Like JAUTEE Nicolas likes this

How can we customise external users format ? 

Is there a documented solution or workaround for how to change the user keys to username for already created users? This is causing issues for me with integrations with Power Bi where the user in a graph is just showing JiraUser****

Like JAUTEE Nicolas likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events