-
Suggestion
-
Resolution: Fixed
-
2,064
-
188
-
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
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.
Problem mitigation
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 editingJRASERVER-71859- The necessity to restart the Jira instance after email templates editingJRASERVER-71860- Performance spikes causing Jira outages when editing email templatesJRASERVER-71861- Necessity to access Velocity (.vm) files from the Jira directory causing the process longerJRASERVER-71862- The risk of breaking templates during an upload due to missing filesJRASERVER-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.
Related articles:
- causes
-
JRASERVER-71988 Some notifications will fail on Jira Data Center 8.14.0 instances hosted on Windows
- Closed
- incorporates
-
JRASERVER-1986 select email template per project
- Closed
- is duplicated by
-
JRASERVER-9792 Fully Customisable Notifications
- Closed
-
JRASERVER-15493 Conditional Events + customizable E-mail Notificaiton [REQUESTID:260028]
- Closed
-
JRASERVER-15778 Mapping custom events to new email templates
- Closed
-
JRASERVER-23000 Custom text on subscription e-mails configured through Admin GUI
- Closed
-
JRASERVER-24734 GUI in Jira for editing Velocity Email Notifications
- Closed
-
JRASERVER-27547 Customise e-mail templates trough administration
- Closed
-
JRASERVER-29375 Sharing Issue template customization
- Closed
-
JRASERVER-46021 Reduce number of support emails
- Closed
- is related to
-
JRASERVER-73132 Using velocity templates within the EmailBuilder causes an exception in a Data Center installation.
- Gathering Impact
-
JRASERVER-14240 Upgrade without manual (re)placement of customized JSPs/Templates/Plugins, etc
- Closed
-
JRASERVER-15925 Text emails include a condition not to display issue priority value. This should not be the case.
- Closed
-
JRASERVER-22206 Priority should be displayed in text email notification even if it is not the system default
- Closed
-
JRASERVER-62063 Different Email Template for each issue filters.
- Closed
-
JSDSERVER-284 As an Admin I want to be able to customise the Service Desk mail templates through the GUI
- Closed
-
CONFSERVER-40684 Create an Email Template Editor in the UI
- Gathering Interest
-
JRASERVER-161 Be able to customize outgoing emails per project
- Future Consideration
- relates to
-
JRASERVER-34193 JIRA notificaions in the apropriate language based on the location.
- Closed
-
JSDSERVER-218 Provide the ability to customize Jira Service Desk notifications
- Closed
-
JRACLOUD-7266 Provide ability to customise email templates that are used for notifications and subscriptions
- Gathering Interest
-
JRASERVER-4451 Make email headers editable in notification templates
- Gathering Interest
-
GHS-55654 Loading...
-
YET-73 Loading...
-
YET-82 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...