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 have a client with an interesting problem that is probably quite common but I have not had to address it before.
They have an IT Helpdesk that supports their internal user base. However, for various reasons, they also allow users to submit tickets from personal accounts. This means that if Sally Smith is an employee and she submits a ticket from firstname.lastname@example.org, Jira creates an account for her with the same name as email@example.com. This creates two entries for "Sally Smith". It makes it very difficult for someone who then later wants to assign Sally Smith to a ticket or @mention her to pick the right user.
What would be really helpful would be if Atlassian would show the domain associated with the account when selecting a user from a user pick list. They wouldn't have to reveal the entire name, but knowing the domain would help to disambiguate the user.
Any ideas how to address this? What have you done in this situation?