We have a new Jira Service Project in Coud which registers tickets by e-mail requests.
My current concern is how to make it scalable. According to old ticket you can make alias e-mails and attach them to the main e-mail one : https://community.atlassian.com/t5/Jira-Service-Management/Configure-more-than-one-email-channels-in-a-project/qaq-p/690096
I want that Project e-mail will stay ex. email@example.com but it still would be able to create tickets from e-mails which in future would be ex. firstname.lastname@example.org or email@example.com .
Unfortunately i maybe have 6 months experience with Jira and i don't know how to set it up.
All help or guide links are appreciated.
Thank you in advance.
Hello @Sten-Reijo Kivi !
Welcome to the community, let's try to get you going.
You are definitely on the right path, however, this is something that has to be configured outside of Jira / Atlassian. You can create e-mail aliases in (for example) Exchange. This will allow e-mail send to those aliases to end up in the inbox of marketing.
Since the marketing account is connected to Jira, e-mails send to that account will be added as an issues.
Unfortunately, Jira has no advanced e-mail options build in. You can therefor not see who the original recipients were and trigger automations on those conditions. There are however, other options to check if you need to (sender address for example). I am also quite sure there are third-party plugins available. Personally I don't have that much experience with third-party plugins and tend to either solve it with build in tools, or postpone the implementation until it is available.
Is this what you are looking for or do you have any other questions?
Thank you for your fast response. I will contact our Exchange specialist to see how it would work.
My biggest concern is that if e-mail came from Issue Reporter through firstname.lastname@example.org then after ticket creation all comments would also move back to reporter through pipeline
email@example.com ->firstname.lastname@example.org -> Issue Reporter
This is, unfortunately, not a scenario that you have to worry about.
Jira notifications are send from a single address. By default this is a jira@ORGANIZATION.atlassian.com address, but you can add a custom address per project.
This means that the communication goes as follows:
Incoming: issue reporter > email@example.com / firstname.lastname@example.org / etc > email@example.com > JSM project
Outgoing: firstname.lastname@example.org (can be changed, see below) > issue reporter
The outgoing mail is handled by the Atlassian servers and won't go through your company mailservers.
Please follow the steps as described in this article to add a custom e-mail address:
What are the steps for setting up custom email addresses
Make sure to follow all the links in the article to get started.
If you want to separate the different mailboxes, you need to create separate projects for the different regions. You can re-use all the settings of another project to save some setup time.
Good luck setting it all up, please reach out if you need any assistance.