Hello
Currently every email notification that comes out of my Jira service project has the same subject line: Jira Request: ${issue.key} - ${issue.summary}
Is it possible to edit the subject based on the type of notification. For example: if this ticket is updated:
Subject line should be: UPDATE: Jira Request: ${issue.key} - ${issue.summary}
Thank you
As Frederic wrote, this isn't possible out of the box. However we do support custom subjects if you send emails using our app Notification Assistant for Jira
Hi Nicole,
From my experience you can't change the template of an email sent from the Notification scheme in a cloud environment.
The Notification scheme, accessible only by JIRA admin, can't be changed. You can only add or delete recipients.
Then, there's the Customer Notifications, that are per-project, which can be edited. But there's only a limited amount of triggers (and "An Issue is updated" is not one of those triggers). Also, Customer Notifications can only send notifications to reporters and customers involved in a request. So not a lot of configuration available here.
The last suggestion is to create an automation. You can delete all the recipients of an event in the Notification scheme (let's say Issue updated) and then create an Automation that will run each time an issue is updated and send an email. It is possible to configure the email by using HTML code and smart values.
But, this email will not be exactly the same, visually speaking, as the ones that are send by JIRA from the notification scheme.
Those seems to be your only options for now. I could be wrong and I hope that we'll get more flexibility in the future but for now, automation seems to be the way to go.
Frederic Chartrand
FMX Solutions - Gold Solution Partner
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Show up and give back by attending an Atlassian Community Event: we’ll donate $10 for every event attendee in March!
Join an Atlassian Community Event!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.