You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I'm testing migrations from Jira server to the Cloud and have this error, where Jira Cloud displays hex versus the name of the assignee. See the attached picture.
How can this be fixed to show the Assignee name and not hex?
This change actually happened back in 2019 and as I vaguely recall was a pretty big deal back then.
To summarize it from a completely ignorant American POV, the EU is a lot... pickier about how user-identifiable information is stored on the Internets. So to satisfy the General Data Protection Regulation, Atlassian made changes so that usernames in the Cloud (ex: darryllee) are now replaced with accountIds (the hex codes you are seeing in your filters).
Ironically, I found some better documentation about the change in a third-party add-on:
It definitely does cause some pain in trying to easily identify who a filter is referring to, and it complicates things when trying to do fancier stuff with Automation, like having to call an API endpoint when you are trying to determine a user's ID based on their email address. (Example.)
Ok found some good documentation of this change on the Developer website, so it talks about REST API changes, but since all your favorite apps had to adjust to this change, it's probably a good reference for everyone:
One last thing - if you're trying to figure out who an particular Account ID refers to, you should be able to pop this into your browser:
That API call will return a JSON blob that includes handy info like emailAddress, displayName, avatars, etc etc.