Hello I am trying to configure email handler to add comments to existing issues.
When a default jira notification is sent to email address, when I reply on email it adds nicely to an issue as a comment.
But default notifications are to simple and will not work.
Notifications configured in automation can be programmed exactly as I want to, but when people reply on that notification email, the comment won't be added and another issue will be created.
I can't to figure it out, do I need some plugin or can it be programmed ?
I've read that i have to have an issue key in email subject to properly be added as a comment, does it mean that if i put it there, and someone hit reply button on that message, it will be added as a comment?
OOOK I wanted to close this topic now, appears that you only have to put issue.key in the email subject and everything works.
Hi @Szymon Ptak
Welcome to community! You're using two different systems, so your aim has to be fined tuned in a such way that would conform to that requirement. Jira incoming handler is designed to handle notification as it adds a header "In-reply-to" to track the email thread in order to distinguish between a new request and an old one and also it scans the subject for issue key. However, if you're using automation to send notifications, that's a completely different notification platform therefore it can't tell or relate the same information to Jira incoming handler. With automation you have to define a way to add the issue key within the subject of the notification, so it can tell when a reply comes in. I prefer you add this prior to when the notification is actually sent the first time.
However on cloud, the Jira notification template can't be configured. JSM notification template on the other hand can but works with JSM customer only users.
So it depends on what exactly you want to achieve. Do you need your customers only users to receive nice customer templates in notification or Jira users should be receiving such notification templates? As the latter isn't feasible.
I have the exact same issue as Szymon.
However, we have just switched to the cloud version of JIRA after many years of the other version (sorry, I don't know the jargon).
After the initial ticket is created, we need any reply to or from the customer to be cc'd as a comment.
Yes. The email address is in the TO field and
Yes. The Issue Key is in the subject line.
Where are the settings to make this happen?
@Prince Nyeche I'm having a very similar issue, wondering if you might have some insight.
Implemented custom notifications using ScriptRunner for JIRA (Cloud), for Request Participants being added and Organizations being added.
The custom notification cannot be replied too for the reasons you outlined above, is there a way for me to specify the "in-reply-to/reply-to" header when sending out the notification via the REST API ?
Failing that, what other ways can we allow customers to be able to reply to the custom notification?
Thanks in advance,
Hey @Kim Fain
Are you referring to Jira default notification or one created by automation? I think all you need to do prior to when the notification is going out, is to provide the issue key on the email subject.
Hey @Mark O_Shea
I'm not sure how you can specify the "in-reply-to/reply-to" header with script runner. I think most probably you need to set a new header (with the details of the reply-to) when posting the notification but I may be wrong.
Hi @Szymon Ptak ,
The issue key in the subject is indeed how Jira will recognize the issue and add it as a comment.
You'll only have to make sure that the reply goes to the email address that your email handler is looking at.
I don't believe the automation email address will act as a handler (it comes from another address)
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events