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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

JIRA GDPR user_key - half users correct, half incorrect?



I have an issue with our 8.4.0 Jira Server instance and I'd need your help with it.

We installed this version in 10/2019 and since then it is creating user_keys for our users based on the GDPR compliant solution, so every new user gets a JIRAUSERxxxxx user_key. But, the older users who have had access to Jira prior to the mentioned date still stayed the same, they have their old user_key which is their company unique identifier - so not their name, like johndoe, but a code like this: u12345, also GDPR compliant.

How do I begin to sync this in the DB? Either solution is ok for me, so whether everyone gets a JIRAUSER id or we feature the company uid in their user_key field is both fine, only it needs to be consistent. 

The problem came to light when trying to import test cases to Zephyr with assignees, Jira simply did not find those who have JIRAUSERxxxxx user_keys as we were identifying them in the excels with their company uid. With thousands of imported test cases, it is quite bothersome to fix by hand every time.

Thanks for the help in advance,


1 answer

@veronika.toth , hey!

Take a look at the app_user table :)

Greetings! We have the exact same problem. Can you give a bigger hint? :P

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events