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.
We are looking at implementing Jira Service Desk but are trying to figure out if we can have multiple inbound email addresses tied to a project.
Right now our customers can email our support team using various email addresses based on issue/department. We would like for all the email addresses to point to a single project and have tickets created and properly routed based on the email address used. Anyone know if that is possible and if so how to go about implementing?
Alias Emails: firstname.lastname@example.org and email@example.com
Jira Service Desk parsing
firstname.lastname@example.org - Category: Benefits - Type: Support
email@example.com - Category: Support Type: Support
If I remove the routing requirement and just say we want all email aliases to point to a single project is that possible?
you could do this w/in your mail service by forwarding all support emails to a single email that feeds JSD. However, then you will not be able to differentiate between the request types. All will come into a single request type, e.g. "support". The portal allows users to select between request types but email does not, it is 1:1.
We have this type of setup with one of our projects. The only way I got it to work was with a mail handler addon. We use JEMH. It allows us to select an issue type for each email and what project the email goes to. Hope this helps.
indeed addons can handle this and JEMH is one of the popular ones.
@Colin Helke Thanks for the recommendation that did the trick in what we were trying to achieve. Another question for you ... we have the tool configured and when we run the Test Case script via JEMH our tickets are created and tagged correctly. However when we try a live inbound email test the ticket is created however the appropriate Component value is not set it is remaining null.
Did you run into that issue at all? Any recommendations?
Reece from The Plugin People here (JEMH vendor), good to see that you are giving JEMH a try!
The problem you describe does not sound familiar, if a component value is configured in JEMH it should be set as long as that component is valid in the related project.
Can you please raise a support request with us directly: The Plugin People Support
Please attach an export of your JEMH profile and your test case to your support request, we can then double check your configuration.
Will do - i can't explain the joy it brings me to get such a prompt response :)
Wow they were fast. I have had great support from them. I was going to suggest to check the audit log within JEMH. You can look at how the email was processed. Maybe it has something to do with permissions. Otherwise I would open a support request.
I'd like to share the suggestion for this feature which is currently under consideration:
If this is important to your use case please vote and if possible add an explanation on how this can impact your production so that we can have a complete picture when considering this feature :)