I'm wondering if anyone has any experiencing managing users with multiple email addresses assigned? Each of our users has (or may have) a userid-based email, ie firstname.lastname@example.org, but also, an alias, ie John.email@example.com.
This causes a problem for us because when people log into the portal, we use their firstname.lastname@example.org - and so the ticket get's opened under email@example.com
Then, when they reply to the email message to continue communication, it comes from John.firstname.lastname@example.org, which ends up opening a new request.
Is there any way to handle this automatically? I can't find any other mention of it, but we can't be the only organization that has this problem.
Currently this is not possible short of having multiple free customer accounts for a user.
It is something we are evaluating, and are keen to learn more about how this is impacting your organisation.
Would you mind voting and sharing your feedback here https://jira.atlassian.com/browse/ID-240
Thanks for sharing your feedback.
For multiple accounts, it is not a great solution, but If you have customer accounts for each alias a user emails you with, and those accounts are a part of the same organisation, and automatic organisation sharing is enabled, you should be able to avoid duplicates.
But I can certainly appreciate this is a lot of administrative overhead.
@Benjamin Paton So we tried to set this up recently - but there is the side effect of all tickets then being fully visible to all others within the "organization". Is there a way to configure this so organization sharing is enabled, but visibility into issues is not?
Hi Ben, we are just trying to allow people to "update" requests from an alias email address without it creating a duplicate ticket.
While what you suggested above does work, but it also allows everyone within the organization to have full visibility into every single ticket.
If it's possible to allow organization sharing with just the ability to update the request, but not to see any ticket details, that would actually work perfectly for us.
You are not the only organization that has this problem. It's a major annoyance for us as well. We try to explain to submitters that they should try to use the same email address from which they normally reply, but that is not something most users really have an awareness of. Plus, they have different aliases configured from different email clients.
My suggested solution is for there to be a feature in Jira Service Management that allows me to add alias email addresses to an end users' profile. That way when emails come in, JSM understands that they're from the same person. Or, better yet, connecting to Google Workspace could do that for me, maybe.
Thank you, Atlassian team, for your time and attention.
Hi Everyone, In this tutorial, we will show you how you can monitor an SLA, and send notifications before or after the SLA has been breached. SLA Threshold Trigger The SLA t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events