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
Why when a user replies to an email ticket message it creates duplicate account for them?
Essentially we have an issue when a user in a customer group responds to a ticket response in JSM via email, it auto creates a new email from the respondent and when user logins to portal and views ticket conversation it does not show his/her dialogue there because the email conversation pulled a users different email when user replied to ticket in email.
There's a long technical essay on how Jira works with emails and how user accounts work and get associated with emails, but you don't really need to hear most of it.
The TLDR version is that Jira knows nothing about email aliases and you should assume it treats every different email address as a unique identifier for an account (it's not really, not any more, but almost all of Jira's behaviour makes it look like it is)
Whne you say "Jira user profiles have their alias attached to them" - that's in your user directory system, Jira isn't looking at them, only the primary email address.
So what is the solution here? Our goal is to not have customers when they respond to a ticket in an email have a new profile and ticket created.
This relates to Jira Software user creation too when they login using the email not used on initial login it creates a new account.
Our current customer users have a company email alias as their email on their user profile. Where most times when they reply to a ticket in gmail the users email actually uses a long-form non-alias company email.
So knowing this, are we to be using an alias, or how can we solve this?
Are we to be only using long-form non-alias emails for customer emails in JSM?
Also, how would this affect Jira Software for this same scenario on issue replying and even when a user logins to Jira with a long-form email it creates a new Jira account for them. As for context here, jira user profiles have their alias attached to them.