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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Seeing dupicate tickets in JSM from email replies all over the community (here, here, here, here, ..) I decided to write an actionable article to get this fixed quickly.
You have received an email from a customer (or they used your service portal).
A different person replies to the ticket emails (or the customer uses a different e-mail address).
Instead of commenting on the existing ticket, a new ticket was created.
Jira ingests emails in five stages, during which problems like a duplicate ticket from an email can occur:
(1) Sending the email > (2) Email Inbox > (3) Jira Mail Handler > (4) Matching the Ticket > (5) Permissions
Jira will not recognize emails from another email address as valid comments, since ..
.. the email address differs from that of the original customer ( => different customer ) and
.. no one other than the original customer is allowed to see or interact with the original customer's tickets (without further setup)
You are using Jira Service Management
The email addesses replying to your tickets are known and you have a relatively stable list (e.g. your customer is an organization)
Will not work if ..
email addresses change frequently (e.g. many individual clients)
There are issues with the other stages
Add all email addresses of the customers who are part of that organization. By doing this, they will be moved from 'general customers' to 'customers specific to that organization'.
Your JIRA admin must ensure the global setting 'Request Sharing' is enabled for your organization:
Global settings (check under this URL):
Project settings (just fyi, no check needed):
New issues created by organization-registered email addresses will now be tagged as such in a dedicated field. Other email addresses registered with the same Organization are now allowed to comment under these issues.
Additionally, if an email has other organization members on CC these are added as request participants, so they will receive notifications regarding that ticket. This does however not apply to people on CC, which are not part of the ticket's organization.
Responding to existing tickets (before Organizations were set up) will however still create a new ticket and not a comment. In order to fix this, you will need to assign them to Organizations in the issue sidebar manually.
Hope this small article helped fix your emailing problem. I'd love to hear if yes or no and also if any particular step caused trouble or can be improved. 🙂
In case this Quickfix did NOT work out, feel free to take a look at Duplicate AI (our app on the marketplace).
It’s an all in one tool all around duplicate issues: automatically find duplicates / similar tickets & merge issues with a few clicks.
– Cheers, Markus / Secretbakery.io
Duplicate AI > Find Duplicates & Merge Issues
3 accepted answers