I'm currently on JIRA 6.4.8 and using JETI 188.8.131.52
I'm not sure if other users encounter this issue, but for our JIRA instance, we have many JQ email addresses configured to different projects and different issue types. Our users love using JETI to send email directly from a JIRA ticket, but they don't always realize that sometimes they're trying to send email from an existing ticket to another JQ email address to create a new ticket in a different project. This is troublesome because JETI doesn't understand that it needs to create the new issue in the different project. Instead, it recognizes the email as a comment on the original ticket the user is sending the mail from.
I've been advising users to Move and Clone the ticket to the new project. It seems that users don't always realize the email address they're sending mail to is configured to another JIRA project.
Is there any way around this?
Unfortunately, there isn't a solution your users are after. However there are a few options to try:
Thank you for the quick response! I will try utilizing the recipient blacklist.
If I add the other JQ email addresses to the blacklist, will the users receive some sort of notification if they try to send mail to an email that has been blacklisted, or will the email just fail at that point?
I previously considered configuring the JETI mail handler with Always Create Issues, but we don't want to lose commenting via email.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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