This is still happening. 

This is still happening. 

This is still happening 

I tested with redirection, but ticket is not created.

Is this still not working? Resolution is fixed ???

I tried also not working why Jira cannot auto forwarding the Gmail!!!

This is also a problem for my and my group. When auto forwarding or redirecting, no new tickets are created. If we manually do it though, it will create the ticket. However, we need redirect through exchange to work so that we can have multiple departments with current email addresses point towards the single JIRA service desk mailbox we created. 

This is a real shame that this doesn't work. Makes the use of Service Desk extremely limited with its email integration.

It's now eleven months since I posted my last comment and it is very disappointing to see that this issue remains unattended and no feedback from Atlassian.

Can someone please advise when this is going to be addressed?

Same here, still not working in JSD 2.5.0.

We're on Service Desk 2.3.5 (still evaluating at the moment) and I found that the issue as described in the original description still persists. No issue created for forwarded mails.
I'm seconding @Mark Matheson to reopen this issue (or create a follow up).

I was pointed to this Issue by the Atlassian Service Desk support team as it seemed to replicate the issue I had raised with them.

Having recently configured Jira and enjoyed the way it allowed me to create multiple Incoming Mail Handlers linked to a single email account, and have them only grab emails that were sent to a particular email alias linked to that account, I was amazed to find that Service Desk did not offer the same functionality.

Atlassian support suggested I vote for this issue in an effort to encourage this feature to be added to the product but I have found I can't as the issue is marked as Fixed.

How is it fixed when I can duplicate the issue in the currently release of Jira Service Desk?

I too am also having an issue with this. I have a rule setup that if mail comes into an address we have declared, then it auto forwards to the (name)@(domain).atlassian.net, it does forward to that address (according to our mail server), however a ticket is not created.

If you send an email directly to (name)@(domain).atlassian.net then a ticket is created

We have experienced the same issue but with Exchange. We have just cut over to Service Desk from using Jira to support our customers. We found out the hard way that the existing aliased email addresses no longer work. This impacts us because our customers have already been set up with their support emails and now they don't work with Service Desk whereas it worked in Jira. I would like to see this issue addressed ASAP.

This is my scenario in more detail:

I am cutting traditional Jira projects over into being Service Desk projects.

The Jira mail handlers were able to create tickets from emails sent to any address as long as they were in the inbox. However, Service Desk doesn't seem to do this. Instead Service Desk seems to only raise tickets from emails that have the configured email address in the TO field.

We use email aliases which appears to be now broken in Service Desk.

For example,
Primary email could be...

abcd@xxx.com.au

which has fictional aliases...

aliases1@xxx.com.au
aliases2@xxx.com.au

The mail box user name however would be the account ID like, for example:

mb344447aw

When sending individual emails to all three addresses, I only get one ticket raised. From my example that would be the primary email (i.e. the one configured in the Service Desk mail handler).

So either we need a way to add additional Service Desk mail handlers or, be able to add alias email addresses to the existing mail handler.