Is there a way to capture the To: field on incoming service desk requests?

[Benjamin Peikes]

We would like to be able to give out email addresses like:
external-vendor+tommyhilfinger@our_company.com

To our vendors, and have notifications from those email addresses create tickets in a service desk, and then use automation to route them to the right place.

This is better than trying to keep track of the email address that these vendors send from.

Is there any way to capture the "To:" field in the incoming email and use it in an automation rule?

How about using something other than a service desk?

[Joseph Chung Yin]

@Benjamin Peikes -

For your customers who use email route to create their issues, their email address is already a part of the his/her account against your JSM projects.  So typically, they will be the issue reporter by default.

Are your site setup to allow anonymous access?  When those issues got created, who is listed as the reporter?  Please advise.  So we can further suggest the better option to address your ask.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

[Benjamin Peikes]

These arent really customers, they are external vendors with notification mailing lists. We want these notifications to create either service desk, or regular Jira issues.

The issue is that we do not know what email their notifications will come from, but we do control the email we provide to them.

We would like to be able to route tickets based on the email address provided to them without creating multiple service desks, or multiple incoming mailboxes.

It would be great if either JSD captured the To: field in requests created via email, or if Jira “Mail Handlers” could capture the To: field into a Jira field.

[Joseph Chung Yin]

@Benjamin Peikes -

Question still - Who is the issue reporter in your JSM project?  So, those external vendors are not the issue creator?

Please advise.

Best, Joseph

[Benjamin Peikes]

We currently are using a Mail Handler, and creating Jira issues (not JSM), but the issue is, the reporter has to be fixed in a mail handler if the incoming email is not one of out Jira users.

Looking at switching to use a service desk to do this. Yes, in the case of using JSM, the reporter will be an “external vendor”. The issue is that we will not be able to know what the “From” email address will be because the emails will be coming from the vendors mail list system.

The idea is that when we give the vendor an email to get notifications of changes to their system, we want to give them a custom email address in our domain. That would mean we always know which vendor the email is from.

So is it possible? Are there any 3rd party addons?

[Joseph Chung Yin]

@Benjamin Peikes -

Are you saying that currently, the issues created in your Jira project based on the incoming emails (vendors) that you default to some common user account?  (i.e. one common user per each vendor).  This means that you are using up an actual Jira Software user license for each vendor.

In JSM implementation, each user (customer) is setup with his/her own account which it is free to submit request into the JSM project.  Only agents from your org (who is handling/processing the issues) will required an actual JSM license.  If you go with the JSM route, then notification is automatically send back to the customer who submitted the case, thus his/her account should always be using his/her email address from his/her company.  You can also configure it to allow users from the same vendor/org to access their issues (i.e. sharing the issues) via the portal UI.  You can use JSM to capture all the issues reported from users within a specific vendor/company via some types of report/data analytic setup.

I am not aware of any third party addon that give you what you are asking for.

Best, Joseph

[Benjamin Peikes]

No, right now, we have an email handler that pulls from a single mailbox. All issues sent to this mailbox trigger the creation of an regular Jira ticket, (not JSM). Because of the way that Atlassian implemented mail handlers, the issues created are created under one of our Jira user accounts.

One of the reasons we don't use JSM for this, is that it's developers and infrastructure people who handle these notifications. They are not two way discussions with external clients.

In either case, it seems like Jira does not capture anywhere the "To:" field when processing incoming email, which means you can't use "To:" based routing. We can't use "From:" based routing because when we signup with a vendor to receive notifications, we do not know the email address that the emails will be sent from. Vendors can change those emails when ever they want and we would not know.