Hi Guys,
We are currently using Jira to manage all our support requests, and we use an email address (which has our company's email domain) as an email for email requests.
All the automatic replies are sent from jira@beakon.atlassian.net, which is fine as long as users simply reply to those emails, as it creates a comment in the issue; but if they send a new email to this jira email address nothing happens and we have no way to track who is sending emails to jira@beakon.atlassian.net.
Now, I have tried changing the email address used to send automatic notifications, but I am getting "DKIM validation failed for this domain.", and I think that is because we are using GSuite. Is there a way we can change this to our email address or, alternatively, simply access the "jira@beakon.atlassian.net" email address this monitor these emails?
Thanks!
Community moderators have prevented the ability to post new answers.
Dear @Beakon Support,
you can configure one default reporter for the email handler when somebody writes a mail to that address that is not a user of the system. But these users will never get mails when you comment the issue.
Regardless what you configure for your email handler, if Jira can identify any issue key the mail body is attached to that existing issue, when the reporter has the permissuin to create issues. Only when no issue key is found a new issue us created at the configured project (Create and comment handler).
So long
Thomas
So there is no way for me to monitor the emails that go to our jira email address? Some users assumed that was our support email address as they were receiving notifications from it, and therefore started sending support requests to that email address that I have no way no monitor.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Set up a "incoming mail" project with an email handler that reads all the incoming mail.
As Thomas says, anything with a subject containing a Jira issue id will then become a comment, and stuff without it will create issues in that project. It is not ideal, as really you want email handlers to cope with all email in the right projects, but at least you will be "monitoring" the incoming mail.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
and where does it get the E-mail from?
Having this issue where If I send an Issue to my JIRA@...... From a user, it works but when I do it from a non user, it doesn't work (Issue still goes through, but the user never gets the comment / reply or confirmations like the registered user did).
Please help
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
also, I am confused on :
Reporter
Initiator
Asignee
ETC......
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear @Bruno Sergio Pongetti Goldemberg ,
you can configure a mails handler here:
https://mydomain.atlassian.net/secure/admin/IncomingMailServers.jspa
after you connected to a mail server, follow then this instructions.
If the sender is a known user, the email will be converted to an issue with the sender as reporter. If the sender is unknown and the option "Default Reporter" is set, then the issue is created and:
When an issue is created using the default reporter, the original sender's address will appear in a brief message at the end of the issue's Description field.
Only when the reporter is a known user (consumes a license) it gets notified. That's Atlassians concept. If you have loads of customers (that do not need to have accounts), then have a look at Jira Service Management.
So long
Thomas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
it did not help at all, sorry :(
I am still with same issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear @Beakon Support ,
can you please open a new question, where you describe your current problem, with as much details about what you tried already?
I will lock this question.
So long
Thomas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.