This observation may not be a bug, per-se, but it's certainly something users will want to avoid.
Some of our Service Desk inboxes have multiple aliases for the same box. For example: email@example.com, firstname.lastname@example.org, ...
When a user e-mails the one of these aliases, the alias is added as a customer and listed in the ticket participants.
In the event of any comment notification -- the notification is e-mailed to the alias e-mail address participant, which is routed back to the Service Desk inbox and treated as a new comment, which triggers another round of notification.
This looping can be pretty high speed, and cause a great amount of customer frustration.
I solved by adding a ScriptRunner script to remove any inbox alias from the participant fields.
Has anyone else encountered this?
In your mail handler do you have it set to create new users? To check this you'll need to go to System Administration > System > Incoming Mail Servers > Mail Handlers and view the JIRA Mail Handler.
If that is checked, try unchecking the create new user box and see if the behavior continues. As you can see from the Creating issues and comments from email knowledge base article and the Managing the email channel knowledge base article these are two different email channels and they behave differently.
Let me know if that helps.
The Jira Service Desk marketing team is working on a guide to help new Atlassian customers switch from email to JSD and we'd love to hear from you! Please share: - What made you realize that i...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs