-
Bug
-
Resolution: Fixed
-
Low
-
2.0.2, 2.1-OD-04
NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.
As quoted from this documentation
You can only link one email account with JIRA Service Desk. If you use more than one email address to interact with your customers and want to integrate them with JIRA Service Desk, you might be able to achieve this by setting up forwarding rules or aliases.
However Gmail's auto forward and aliases doesn't work. These mails are ignored and request are not created
Steps to reproduce
- Install Service Desk add-on (I tested with v 2.0.2)
- Create new Service Desk
- Navigate to Settings > Email settings
- Turn on email request and enter valid credentials (eg. servicedesk@gmail.com)
- In your secondary gmail account (eg. servicedesk-backup@gmail.com), configure auto forwarding to servicedesk@gmail.com
- Send an email to servicedesk-backup@gmail.com
Expected Results
- servicedesk-backup@gmail.com will receive the email and automatically forward it to servicedesk@gmail.com
- servicedesk@gmail.com will receive the email
- Mail handler will process the email and create the request in Service Desk
Actual Results
- servicedesk-backup@gmail.com receives the email and automatically forward it to servicedesk@gmail.com
- servicedesk@gmail.com receives the email
- Mail handler doesn't create a new request in Service Desk for this email
Notes
- I personally tested this auto forwarding feature
- I was unable to test aliases, but there are cases where a customer configured aliases and the mail handler ignores the email
- If you manually forward the email, it will be processed. Problem is with gmail auto forwarding
- is related to
-
JSDSERVER-1040 Cannot handle 'bulk' or email not specifically sent to service desk support email
- Closed
-
JSDSERVER-1041 Forwarding emails from a private inbox to service desk
- Gathering Interest
- relates to
-
JSDCLOUD-834 Alias email and auto forwarding does not create new request in Service Desk
-
- Closed
-
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
Page Loading...
-
Page Loading...