Status: Closed (View Workflow)
Fix Version/s: 8.14.0
Component/s: Email notifications
Support reference count:188
Current Status:Atlassian Update – 27 November 2020 Hello everyone, Thank you for your votes, comments, and patience on this issue. We are glad to announce that enhancements related to email template editing have been included in the 8.14.0 release! We hope that with the above, the process of editing templates will be more convenient, and user-friendly. Please take a look at the Problem Mitigation section under the Description of the issue to read about all areas we have addressed. Thank you, Damian Reweda Senior Product Manager, Jira Server and Data Center
Original request description:
As a JIRA administrator I want to make sure that the notifications sent from JIRA are actionable and reflect the recipients' expectation related to the content and format. I can change current JIRA email format by manual editing of velocity files, but that is not an efficient way of doing so, and it is not supported for Cloud instances of JIRA.
What I need is an email template editor in JIRA's web-interface so that users can create customised email templates that are used for notifications and subscriptions.
It would also be ideal to have the ability to create and manage multiple email templates which could be then assigned to the relevant filter subscription or notification.
When deciding to address problems related to email template editing, we went carefully through comments to understand all the pains that were pointed out. As an outcome, we have made a decision to implement a multi-step approach to the suggested problem.
The problems that we have heard repeatedly and decided to address them:
JRASERVER-71858- Lack of comprehensive documentation to support syntax understanding and templates editing JRASERVER-71859- The necessity to restart the Jira instance after email templates editing JRASERVER-71860- Performance spikes causing Jira outages when editing email templates JRASERVER-71861- Necessity to access Velocity (.vm) files from the Jira directory causing the process longer JRASERVER-71862- The risk of breaking templates during an upload due to missing files JRASERVER-71863- Extra work required after each Jira upgrade to keep email templates up-to-date
As many of our customers appreciate the flexibility of having the ability to edit email template files itself, we have decided to:
- move the Velocity (.vm) files from the Jira directory to Jira home so that any upgrade of Jira will be smooth without an additional, manual effort;
- support the process of email editing by performing the majority of actions through Jira UI - downloading, uploading the templates package;
- mitigate the risk of breaking emails - the system will verify if all required files are included to make sure that the risk of breaking emails is reduced;
- provide documentation that should guide through the process of editing.
We are open to hearing additional feedback and we would love to hear customer’s voices. With that, we have decided to open a JAC ticket as the outcome of the feedback we have received from you:
- JRASERVER-71864 - As a Jira administrator, I want to test email template changes before deploying them to production
We encourage you to review the release notes, test the newest enhancements, and let us know here on in the ticket above (or any other related ticket) about any additional problems you are still experiencing.