we have the following use case which I am guessing is common enough:
A non-user e-mails a problem/request into JIRA. This creates a new issue. In order to have subsequent e-mails inserted as comments and not create more new issues, the non-user needs to include the issue key in follow-up e-mails.
So, the non-user needs to somehow get an ACK e-mail back with the issue key. This I believe should be done automatically: "Hi, your issue has been registered as ABC-1234. Please use this when ....."
I would expect the functionality to do this in JIRA (OnDemand) would be as follows:
The sender's e-mail address is mapped to a custom field (e.g. "Sender's e-mail") by the Mail Handler. The Notification Scheme will use the custom field to send an e-mail to the sender upon issue creation.
What's missing it seems is that it is not possible to configure the Mail Handler to save the sender e-mail address in a field. Yes, a new user can be created, but these are in principle anonymous users that will only register issues once or twice, ever.
Furthermore, the Notification Scheme does not allow free text fields as the source of an e-mail address. (Only Group Picker or Multi Group Picker are allowed according to the docs).
Have a missed something? Is it possible to implement this use case?
Hi Kevin, i think you may want/need to write your own custom mail handler.
This class can be copied from Atlassian;s existing examples, and modified to save the senders email in a custom field.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
A picture tells a thousand words. And agility boards have just released their latest feature: cover images on issues – so now your board can tell a story at first glance. Upload attachmen...
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