|
The ${email} parameter is being expanded as the user's email address (e.g. user@company.com).
The problem with the way it is now, is that when someone gets a notification, they naturally click "Reply". Two problems arise: 1) the reply-to is not a real person – it's the project address, so people don't realize that right away. 2) Outlook doesn't let you click in the middle of the string to just get the person's email address. As to not showing the project's email address - I apologize, that is indeed showing, by default, without need of a variable. Anyway, it's a minor issue, you can resolve as Won't fix if it's not something you can work around. Cheers The best solution is to a) establish a POP box so that email replies become comments on the issue, b) modify the From address format to make clear that replies will go to JIRA (and indirectly the original message sender). If "Joe Bloggs (JIRA)" does not convey this to your users, then try "JIRA (from Joe Bloggs)" or just "JIRA".
The ability to set the From address to the real user's would also avoid problems with mail archivers like ezmlm which group mails by the actual address (jira@smtphost) but under the name of the first instance ("Joe Bloggs (JIRA)"). See http://issues.apache.org/jira/browse/INFRA-370
Similar to the above comment, sophisticated address books like Emacs' bbdb will issue a warning about the sender's name (the one previously associated with the email address) has now changed. So if I have John Doe in my address book, but suddenly I receive an email from John Doe (actually from Jira), it prompts me to make jira@company.com an alias for John Doe. But it prompts me for every single user who changes something in Jira.
IMHO, it's poor form to misrepresent a user's actual email address in a message. It should at least be a configurable thing. Jim,
Try setting bbdb-quiet-about-name-mismatches (bbdb docs http://www.atlassian.com/software/jira/docs/latest/issue_creation_email.html > IMHO, it's poor form to misrepresent a user's actual email address in a message. It should at least be a configurable thing. The degree of 'misrepresentation' is up to you. In jira-application.properties you can set the From: format to '<jira@company.com>', 'JIRA - Joe Bloggs <jira@company.com', 'JIRA on behalf of Joe Bloggs <jira@company.com>' etc. The actual address used cannot be changed yet, which is the subject of this issue. The fact we can't 'reply' to the user who originally made the change is a pretty large dissatisfier. We have a generic email account established which we have to monitor to make sure no one 'accidentally' replies to the email message. I will incorporate your band-aid solution of changing the email name to 'on the behalf of' as an attempt to lower the occurrence. We would definitely love to implement the Issue/Comment Creation from Email, but unfortunately there is no exchange server (POP server) in our networks, only relay servers which do not actually hold any e-mails.
Thanks for you help. > We would definitely love to implement the Issue/Comment Creation from Email, but unfortunately there is no exchange server (POP server) in our networks, only relay servers which do not actually hold any e-mails.
How do people get their mail delivered locally then? Presumably either POP or IMAP is used, in which case it shouldn't be a big deal to have a jira@<company>.com email address added. I'm adding my vote to be able to change the reply-to to the actual user which should not be a big deal given that JIRA has already this info. Yes I understand you prefer emails to become new issue comments but people reply to a notification to communicate "out-of-band" information or request, ie. something of interest to both party only.
If you really intend not to provide it for some reason please update this issue as "Won't fix". I also added my vote. We have made various other source code modification to Jira and I also made this one for our company.
If anyone else is modifying the code themselves and wants to make this change see my query in the forums at http://forums.atlassian.com/message.jspa?messageID=257245479#257245479 We would like the ability to configure the "reply-to" header:
We have found problems with outlook "cleverly" resolving the sender address from the GAL, and so all emails appear to come from the "Full Name" of the account created for Jira in Exchange. Outlook is trying to be helpful and reduce spam by preventing spoofed emails for addresses it can lookup in the GAL. Currently, I have to send emails from an invalid address, so that the emails arrive (spoofed), with the name of the person who "commented" or "updated" the issue displayed correctly in the outlook inbox. This prevents users from replying to emails and having them come back into jira... If I could change the reply-to address, I would be able to configure the replies to come back to Jira, but the sender address be a non-GAL address, which would spoof correctly. Us too! Recipients naturally click Reply-To and the email bounces (at best) or goes into a black hole (at worst).
We do not want to set up a 'jira@company.com' email account because who will read it? We dont want it to be a mailing list, because everyone in a project would need to be on it. I note this dates from 2005; is it actually (going to be) considered for implementation? |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
At the moment there is no way to set the reply-to header to the address of the user doing teh change. We find that it is better to keep all the ocmmunication in the system. So if you setup JIRA to create issue or add comments from e-mail replies as described here:
http://www.atlassian.com/software/jira/docs/v3.2.2/issue_creation_email.html
all of the communication will be kept in JIRA and will not be 'lost'.
I hope this helps. Please let us know if you have any other questions or would like more information. Otherwise please resolve this issue.
Thanks,
Anton