Uploaded image for project: 'JIRA'
  1. JIRA
  2. JRA-7266

Create an Email Template Editor in the UI to Replace Editing Velocity Templates

    Details

    • Feedback Policy:

      JIRA feedback is collected from a number of different sources and is evaluated when planning the product roadmap. If you would like to know more about how JIRA Product Management uses customer input during the planning process, please see our post on Atlassian Answers.

      Description

      Atlassian Status as of 5 November 2014

      Hi everyone,

      Thanks so much for your votes and comments on this feature request. While this feature is still on our radars, we won't be adding this feature in the near future.

      • For JIRA Server customers, the velocity templates can be edited so there is a way to accomplish custom email templates, though we realize that it does add more work to JIRA upgrades.
      • Please also see Andy's comment on how to use the JIRA Enterprise Mail Handler plugin for easier ways to customize email templates for external mail users.
      • You can also try our free Atlassian Labs plugin, available here and provide us with your feedback and comments. This plugin is only available for JIRA Server and is not officially supported or maintained by Atlassian.

      We realise neither of these help our Cloud customers, so if you are a developer yourself, you should definitely take a look at our Atlassian Connect platform which opens a path for JIRA add-on development for Cloud instances as well. Let us know if you need any help.

      Thanks for your patience and we hope you appreciate our open approach to feature requests.

      Cheers,
      Dave
      JIRA Product Management
      dmeyer@atlassian.com

      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.

        Issue Links

          Activity

          Hide
          admin260 Morten Breiner added a comment -

          Andy, thanks for pointing this out, much appreciated.
          However, I do agree with Brady's comment too. This is a must have functionality and should be supported in all JIRA instances.
          Cheers,
          -Morten

          Show
          admin260 Morten Breiner added a comment - Andy, thanks for pointing this out, much appreciated. However, I do agree with Brady's comment too. This is a must have functionality and should be supported in all JIRA instances. Cheers, -Morten
          Hide
          elvar Elvar Bjarki Böðvarsson added a comment -

          Just everyone remember that the visual workflow editor used to be a third party plugin and then Atlassian bought it. Some features are just too important to the functionality to not be a part of the core product.

          Show
          elvar Elvar Bjarki Böðvarsson added a comment - Just everyone remember that the visual workflow editor used to be a third party plugin and then Atlassian bought it. Some features are just too important to the functionality to not be a part of the core product.
          Hide
          robert.leonard Rob Leonard added a comment -

          I agree completely with Brady Owens comments, and we have taken the same position (using a different support desk solution with better features/functionality) until such time as JIRA/JIRA Service Desk can provide a more complete solution around a support desk product. The notification features in particular need to be enhanced all around for JIRA.

          Show
          robert.leonard Rob Leonard added a comment - I agree completely with Brady Owens comments, and we have taken the same position (using a different support desk solution with better features/functionality) until such time as JIRA/JIRA Service Desk can provide a more complete solution around a support desk product. The notification features in particular need to be enhanced all around for JIRA.
          Hide
          stefan22 Stefan Hett added a comment - - edited

          Had this on my backlog to check out after upgrading our JIRA instance to 6.0. Was looking forward to be able to use the Atlassian provided (though unsupported) plugin so to remove the upgrade step to modify/check the subject email templates upon each upgraded version just to readd the event-type to the subject line again...

          Unfortunately as stated in other comments the plugin hasn't been maintained ever since JIRA 6.0.8 and therefore we won't evaluate it (since for the described case above it certainly won't help us).

          I'm sure that the mentioned 3rd party plugin here is a great tool, but for just re-adding the event-type to the subject line of JIRA notifications I'm sure I'll have a hard time in convincing my boss to invest in that plugin.

          Hence I've to second all the other statements here: IMHO a certain amount of email templating/customization capabilities should certainly be a part of JIRA (at least providing the features which were available in earlier JIRA versions already)....

          Show
          stefan22 Stefan Hett added a comment - - edited Had this on my backlog to check out after upgrading our JIRA instance to 6.0. Was looking forward to be able to use the Atlassian provided (though unsupported) plugin so to remove the upgrade step to modify/check the subject email templates upon each upgraded version just to readd the event-type to the subject line again... Unfortunately as stated in other comments the plugin hasn't been maintained ever since JIRA 6.0.8 and therefore we won't evaluate it (since for the described case above it certainly won't help us). I'm sure that the mentioned 3rd party plugin here is a great tool, but for just re-adding the event-type to the subject line of JIRA notifications I'm sure I'll have a hard time in convincing my boss to invest in that plugin. Hence I've to second all the other statements here: IMHO a certain amount of email templating/customization capabilities should certainly be a part of JIRA (at least providing the features which were available in earlier JIRA versions already)....
          Hide
          jace Jace Proctor added a comment -

          As a JIRA Cloud/OnDemand customer, it's pretty crappy that we can't edit the e-mails our JIRA install sends out. If Atlassian wants to continue to try and convert people over to using Cloud, it's going to need to offer feature parity with Server.

          One of the reasons we went with JIRA is because we could get the product (JIRA) without having the headache of maintaining our own installation, versus other project management solutions, like Hansoft. We're running into instances time and time again where JIRA has a deficiency or much-needed feature that's been solved ages ago (either by Atlassian or by a Server plug-in), that hasn't been ported over to the Cloud product. Atlassian won't fix it because there's a Server fix that's worked for ages, but the Cloud customers are left in the lurch.

          Show
          jace Jace Proctor added a comment - As a JIRA Cloud/OnDemand customer, it's pretty crappy that we can't edit the e-mails our JIRA install sends out. If Atlassian wants to continue to try and convert people over to using Cloud, it's going to need to offer feature parity with Server. One of the reasons we went with JIRA is because we could get the product (JIRA) without having the headache of maintaining our own installation, versus other project management solutions, like Hansoft. We're running into instances time and time again where JIRA has a deficiency or much-needed feature that's been solved ages ago (either by Atlassian or by a Server plug-in), that hasn't been ported over to the Cloud product. Atlassian won't fix it because there's a Server fix that's worked for ages, but the Cloud customers are left in the lurch.

            People

            • Assignee:
              Unassigned
              Reporter:
              ben@atlassian.com Benjamin Naftzger [Atlassian]
            • Votes:
              803 Vote for this issue
              Watchers:
              396 Start watching this issue

              Dates

              • Created:
                Updated: