JIRA
  1. JIRA
  2. JRA-7266

Create a web-based email template editor - rather than having to edit Velocity templates

    Details

      Description

      Atlassian Status as of 4 March 2014

      Hi everyone,

      Thanks so much for your votes and comments on this feature request. While this feature is still on our roadmap, we won't be adding this feature in the next 12 months.

      • For on-premise JIRA 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 customers who host a downloaded version of JIRA.

      We realize neither of these help our OnDemand customers, so we still want to address this, either in a JIRA feature or making sure third party solutions can be made available to OnDemand customers.

      While we will not be addressing this feature in the next 12 months, we plan to resolve several other top voted feature requests in the next 12 months, including JRA-3156, JRA-3821, JRA-1431. And we have recently resolved JRA-32199, JRA-32200, JRA-2703 and JRA-7659 as well as provided the first drop of functionality related to JRA-3157.

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

      Cheers,
      Bartek
      JIRA Product Management
      bartek (at) atlassian (dot) 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 OnDemand 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
          tim feeley added a comment -
          1. I'm not sure if this is within the scope of the issue, but if this utility would allow us to edit the email template mappings (for creating and managing custom templates), that would be handy.

          2. This second area I think is a bit more complex but I think it might be a good way to provide some customization functionality without users having to have to muck too much with the source code. Instead of specifying the template in the context of an Event, there should be an opportunity to "override" the template for a particular notification group (see attached screen shot).

            This might be a separate (duplicated) issue, but just my two cents
          Show
          tim feeley added a comment - I'm not sure if this is within the scope of the issue, but if this utility would allow us to edit the email template mappings (for creating and managing custom templates), that would be handy. This second area I think is a bit more complex but I think it might be a good way to provide some customization functionality without users having to have to muck too much with the source code. Instead of specifying the template in the context of an Event, there should be an opportunity to "override" the template for a particular notification group (see attached screen shot). This might be a separate (duplicated) issue, but just my two cents
          Hide
          tim feeley added a comment -

          Additionally, it would be nice if we could specify some variables that Velocity could access within each notification.

          For example,

          Notification Recipient Variable Value
          Issue Created Customers possessive your ticket
          Issue Created Developers possessive a new ticket
          Show
          tim feeley added a comment - Additionally, it would be nice if we could specify some variables that Velocity could access within each notification. For example, Notification Recipient Variable Value Issue Created Customers possessive your ticket Issue Created Developers possessive a new ticket
          Hide
          Josef Karthauser added a comment -

          I've created a subscription email for a list of blocking bugs, which gets emailed daily. Without the ability to change the template it's not clear to the recipients who each bug is assigned to. I don't really care for a completely general solution to change the template, but I would at least want the columns that are included in the issue filter to be included in the email. It seems silly that they're not currently; I consider that a bug.

          Show
          Josef Karthauser added a comment - I've created a subscription email for a list of blocking bugs, which gets emailed daily. Without the ability to change the template it's not clear to the recipients who each bug is assigned to. I don't really care for a completely general solution to change the template, but I would at least want the columns that are included in the issue filter to be included in the email. It seems silly that they're not currently; I consider that a bug.
          Hide
          Ben Kunkel added a comment -

          The element of this that I consider most critical is getting the template mappings into the database so that I don't have to re-implement the changes I make with each JIRA upgrade.

          Show
          Ben Kunkel added a comment - The element of this that I consider most critical is getting the template mappings into the database so that I don't have to re-implement the changes I make with each JIRA upgrade.
          Hide
          Vincent Thoulé (Alkaes) added a comment -

          Hi All,

          Minyaa 2.2 has been just released with new feature for Timesheet Management with an approbation workflow.
          In order to implement a dedicated notification mechanism, 2 new features in Minyaa Core have been introduced, allowing you :

          These solutions requires a small effort in term of development allowing you to integrate your own Notification Types and Mail Templates in a plugin. The definitions will have to be stored as resource and some Classes (1 for Tempate and 2 or more for Notifications).

          For the moment, since these extension are embedded in a plugin, there is not yet an editor, but it is more easy to deploy than applying modifications in existing Template.
          Next step should a Database Storage, probably an editor and perhaps a dedicated Scheme (To follow ...)

          Regards
          Vincent
          Minyaa Team

          Show
          Vincent Thoulé (Alkaes) added a comment - Hi All, Minyaa 2.2 has been just released with new feature for Timesheet Management with an approbation workflow . In order to implement a dedicated notification mechanism, 2 new features in Minyaa Core have been introduced, allowing you : to define your own Notification Type to define your own Mail Template These solutions requires a small effort in term of development allowing you to integrate your own Notification Types and Mail Templates in a plugin. The definitions will have to be stored as resource and some Classes (1 for Tempate and 2 or more for Notifications). For the moment, since these extension are embedded in a plugin, there is not yet an editor, but it is more easy to deploy than applying modifications in existing Template. Next step should a Database Storage, probably an editor and perhaps a dedicated Scheme (To follow ...) Regards Vincent Minyaa Team
          Hide
          Tim Moore [Atlassian] added a comment - - edited

          Because the existing way to customise email content requires editing files inside the webapp directory, we are unable to allow per-customer email customisation in JIRA Studio. Many JIRA Studio customers would appreciate a way to edit the content through the web UI and store it in the database or JIRA home directory.

          See https://studio.atlassian.com/browse/JST-1791

          Show
          Tim Moore [Atlassian] added a comment - - edited Because the existing way to customise email content requires editing files inside the webapp directory, we are unable to allow per-customer email customisation in JIRA Studio. Many JIRA Studio customers would appreciate a way to edit the content through the web UI and store it in the database or JIRA home directory. See https://studio.atlassian.com/browse/JST-1791
          Hide
          A. Gilles added a comment -

          We have frequent requests to edit templates, but since this work has to be redone after upgrading, we discourage it. I think this feature would be really helpful.

          Show
          A. Gilles added a comment - We have frequent requests to edit templates, but since this work has to be redone after upgrading, we discourage it. I think this feature would be really helpful.
          Hide
          Myra added a comment - - edited

          We just upgraded from 4.3.3 to 4.4.4 and the subject-line templates for issue notifications have changed from "$eventTypeName: ($issue.key) $issue.summary" to "($issue.key) $issue.summary". It required a manual fix to reinstate the previous behavior, and it won't be preserved across an upgrade (as noted here). Apologies if I've overlooked this, but I didn't see the template change noted in any release notes or upgrade guides. Adding my vote to this issue.

          Show
          Myra added a comment - - edited We just upgraded from 4.3.3 to 4.4.4 and the subject-line templates for issue notifications have changed from "$eventTypeName: ($issue.key) $issue.summary" to "($issue.key) $issue.summary". It required a manual fix to reinstate the previous behavior, and it won't be preserved across an upgrade (as noted here). Apologies if I've overlooked this, but I didn't see the template change noted in any release notes or upgrade guides. Adding my vote to this issue.
          Hide
          Barry Allard added a comment -

          This is very important to my clients.

          Show
          Barry Allard added a comment - This is very important to my clients.
          Hide
          Dave Thomas added a comment -

          In our organization, we mostly just want to add custom fields to the notification emails. It would be great if there were a simple way to do this without having to worry about carrying this modification over during every single subsequent upgrade.

          Show
          Dave Thomas added a comment - In our organization, we mostly just want to add custom fields to the notification emails. It would be great if there were a simple way to do this without having to worry about carrying this modification over during every single subsequent upgrade.
          Hide
          Daniel Bates added a comment -

          i would like to add a disclaimer to my email templates

          Show
          Daniel Bates added a comment - i would like to add a disclaimer to my email templates
          Hide
          Thomas Reimer added a comment -

          Joining the club of waiting users... It Would be very nice to manage email templates via the web interface. Two things are recently quite problematic:

          1. As I understood you have to restart JIRA server to apply new template->event mappings. Quite difficult when our project members just want to have a new event "on the fly".

          2. JIRA update/upgrade procedure is already difficult enought (e.g. plugin compatibility, icons, modified files, etc.) Managing custom template files makes that even more complicated.

          This feature request is nearly seven years old. Developing a mail template / event mapping component for the administration panel should not be that difficult I guess. So please: You would make many JIRA administrators happy scheduling a solution for one of the next releases.

          Show
          Thomas Reimer added a comment - Joining the club of waiting users... It Would be very nice to manage email templates via the web interface. Two things are recently quite problematic: 1. As I understood you have to restart JIRA server to apply new template->event mappings. Quite difficult when our project members just want to have a new event "on the fly". 2. JIRA update/upgrade procedure is already difficult enought (e.g. plugin compatibility, icons, modified files, etc.) Managing custom template files makes that even more complicated. This feature request is nearly seven years old. Developing a mail template / event mapping component for the administration panel should not be that difficult I guess. So please: You would make many JIRA administrators happy scheduling a solution for one of the next releases.
          Hide
          Andy Brook (Javahollic Software) added a comment -

          Just curious, but does 'template editing' in a browser work for most people? I ask as I'm implementing another event listener (nothing new there) but also per-project template customization as part of JEMH. 3rd party developments don't solve the problem and aren't usable by the masses because JIRA doesn't allow you to disable the default issue listener (ie stopping it from generating an event as well). OK, it is possible with a code change, but that seems enough to put most people off. To enable 3rd party support, go vote on the rather obscure JRA-19957. Its been marked a bugfix release for a long time now...

          Managing configuration between environments is a common problem that Atlassian and plugin developers need to address, customized templates make this even more important, and makes upgrades more difficult. With great customization comes great responsibility (at upgrade time!)

          Show
          Andy Brook (Javahollic Software) added a comment - Just curious, but does 'template editing' in a browser work for most people? I ask as I'm implementing another event listener (nothing new there) but also per-project template customization as part of JEMH . 3rd party developments don't solve the problem and aren't usable by the masses because JIRA doesn't allow you to disable the default issue listener (ie stopping it from generating an event as well). OK, it is possible with a code change, but that seems enough to put most people off. To enable 3rd party support, go vote on the rather obscure JRA-19957 . Its been marked a bugfix release for a long time now... Managing configuration between environments is a common problem that Atlassian and plugin developers need to address, customized templates make this even more important, and makes upgrades more difficult. With great customization comes great responsibility (at upgrade time!)
          Hide
          James Monroe added a comment -

          We'd be happy with being able to customize the Subj line to include the Components of the issue.
          /voted

          Show
          James Monroe added a comment - We'd be happy with being able to customize the Subj line to include the Components of the issue. /voted
          Hide
          Andrew MacNamara added a comment -

          I am not opposed to modifying the Velocity template file, but I simply do not have access to the file system because we have a hosted solution.

          Show
          Andrew MacNamara added a comment - I am not opposed to modifying the Velocity template file, but I simply do not have access to the file system because we have a hosted solution.
          Hide
          Fabrizio Galletti added a comment -

          If possible the personalization should be project related or associated

          Show
          Fabrizio Galletti added a comment - If possible the personalization should be project related or associated
          Show
          Ron Winacott added a comment - I also like Tim's suggestion in comment https://jira.atlassian.com/browse/JRA-7266?focusedCommentId=99946&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-99946 .
          Hide
          Chris Johnson added a comment -

          For us, it's not the editing of the files that is problem, but rather the need to redo those changes after every JIRA upgrade, that is the most important factor. Any improvements which help us make minor customizations and maintain them will be welcomed.

          If Atlassian just made the email notifications mobile-device friendly, that would help as well, since that's our current primary motivation for modifying the templates.

          Show
          Chris Johnson added a comment - For us, it's not the editing of the files that is problem, but rather the need to redo those changes after every JIRA upgrade, that is the most important factor. Any improvements which help us make minor customizations and maintain them will be welcomed. If Atlassian just made the email notifications mobile-device friendly, that would help as well, since that's our current primary motivation for modifying the templates.
          Hide
          Luke Chandler added a comment -

          I'm testing this system for my workplace, a very large organisation - potential for 1000's of users accessing 100's of "projects".

          Happy with all the existing features but the lack of customising email templates within the Jira CMS is a complete deal-breaker.

          Why isn't this a standard feature? I shouldn't have edit code on a hosted server to customise templates. This should be fully customisable robust built-in feature.

          The only reasonable work around I can come up with - that would be easy for staff to do - would be to download an excel file (based on the required filter) at the end of a given period and create a mail merge based on this spreadsheet.

          This isn't good enough based on some pretty broad system specifications, it's the ONLY major let down for Jira.

          Show
          Luke Chandler added a comment - I'm testing this system for my workplace, a very large organisation - potential for 1000's of users accessing 100's of "projects". Happy with all the existing features but the lack of customising email templates within the Jira CMS is a complete deal-breaker. Why isn't this a standard feature? I shouldn't have edit code on a hosted server to customise templates. This should be fully customisable robust built-in feature. The only reasonable work around I can come up with - that would be easy for staff to do - would be to download an excel file (based on the required filter) at the end of a given period and create a mail merge based on this spreadsheet. This isn't good enough based on some pretty broad system specifications, it's the ONLY major let down for Jira.
          Hide
          Matt Doar (ServiceRocket) added a comment -

          @Luke 289 other people agree with you, but I'd use Confluence instead of JIRA if you want a CMS. JIRA is more of a unit-of-work tracking kind of tool.

          Show
          Matt Doar (ServiceRocket) added a comment - @Luke 289 other people agree with you, but I'd use Confluence instead of JIRA if you want a CMS. JIRA is more of a unit-of-work tracking kind of tool.
          Hide
          Luke Chandler added a comment -

          @Matt.
          1. Custom field data into Jira (via webform from external client) - check
          2. Decent workflow interface for internal staff to use - check
          3. Decent reporting tools for managers to use - check
          4. Information OUT of Jira (to our external clients) - non-existent.

          Imagine 100's of different types of "issues", with various complexities submitted by 10,000's of external clients. We want to be able to get back to the client with a notification/confirmation that is customised based on changing the status of their "issue".
          For instance:
          1. client submits Application Form XYZ.
          2. internal staff member reviews application, puts it into another system and changes the issue to be "pending status". - Need to tell the client what's going on!!
          3. internal staff member changes the client's application from "pending" to "approved" - Need to tell the client what's going on again.

          This is where Jira falls down, it only has a notification module for internal staff. No email templates that can be customised, automated and sent to external clients - on a given action. At least if this JRA-7266 was completed, the existing templates could be customised (hopefully per project), with custom fields and html.

          Show
          Luke Chandler added a comment - @Matt. 1. Custom field data into Jira (via webform from external client) - check 2. Decent workflow interface for internal staff to use - check 3. Decent reporting tools for managers to use - check 4. Information OUT of Jira (to our external clients) - non-existent. Imagine 100's of different types of "issues", with various complexities submitted by 10,000's of external clients. We want to be able to get back to the client with a notification/confirmation that is customised based on changing the status of their "issue". For instance: 1. client submits Application Form XYZ. 2. internal staff member reviews application, puts it into another system and changes the issue to be "pending status". - Need to tell the client what's going on!! 3. internal staff member changes the client's application from "pending" to "approved" - Need to tell the client what's going on again. This is where Jira falls down, it only has a notification module for internal staff. No email templates that can be customised, automated and sent to external clients - on a given action. At least if this JRA-7266 was completed, the existing templates could be customised (hopefully per project), with custom fields and html.
          Hide
          Andy Brook (Javahollic Software) added a comment -

          Just to bring my earlier comment up to date. JEMH now has two key features:

          • The Integrated Issue Event Listener allowing per-project generation of email updates to email addresses found in a specified custom field based on events you choose.
          • The Issue Event TemplateSet feature provides a web-based email template editor allowing customized copies of current JIRA per-event velocity templates to be made in both Text and HTML.

          This solution is very specific to supporting external non-JIRA account holders in an automated manner. Unfortunately, due to JRA-19957 it is not possible to replace the default Issue Event Listener without source code changes that would allow third party solutions like JEMH to be used for JIRA user notifications also.

          See a walk-through of the configuration required to support emailing external users here. I'd be interested to find out what people think of how JEMH does/doesn't addresses this particular need.

          Show
          Andy Brook (Javahollic Software) added a comment - Just to bring my earlier comment up to date. JEMH now has two key features: The Integrated Issue Event Listener allowing per-project generation of email updates to email addresses found in a specified custom field based on events you choose. The Issue Event TemplateSet feature provides a web-based email template editor allowing customized copies of current JIRA per-event velocity templates to be made in both Text and HTML. This solution is very specific to supporting external non-JIRA account holders in an automated manner. Unfortunately, due to JRA-19957 it is not possible to replace the default Issue Event Listener without source code changes that would allow third party solutions like JEMH to be used for JIRA user notifications also. See a walk-through of the configuration required to support emailing external users here . I'd be interested to find out what people think of how JEMH does/doesn't addresses this particular need.
          Hide
          Thomas Reimer added a comment -

          Hello All,

          Many thanks for your feedback and votes on this issue.

          We're working on addressing more of the top JIRA feature requests and unfortunately we don't have plans to add this feature into the JIRA roadmap for the next 12 months.[...]

          Hello Bryan,

          thanks for the status update.
          Addressing more of the top JIRA feature requests sounds very good - but I'm sure many JIRA users would appreciate it if you would give us some information which of the recent top 15 requests are on the roadmap for the next 12 month:

          JRA-3821 Priorities per Project and Resolutions per Issue Type
          JRA-4446 Sub-issues should be able to contain their own sub-issues
          JRA-1549 Ability to rename a user
          JRA-846 Support for subcomponents
          JRA-3156 Required: Project Group Administrator
          JRA-5783 Make field required only for one state transition
          JRA-5225 (JRA-18505) Sub-tasks should inherit selectable fields from the parent task
          JRA-1391 Renaming groups after creation.
          JRA-5493 (JRA-18505) Ability to add watchers during issue creation
          JRA-7266 Create a web-based email template editor - rather than having to edit Velocity templates
          JRA-3501 Allow Versions of components
          JRA-1991 Custom fields for Projects
          JRA-2698 Create versions on multiple projects
          JRA-7659 Limit user picker to members of certain groups / roles
          JRA-2703 Not possible to change a project's key

          Regards
          Thomas

          Show
          Thomas Reimer added a comment - Hello All, Many thanks for your feedback and votes on this issue. We're working on addressing more of the top JIRA feature requests and unfortunately we don't have plans to add this feature into the JIRA roadmap for the next 12 months. [...] Hello Bryan, thanks for the status update. Addressing more of the top JIRA feature requests sounds very good - but I'm sure many JIRA users would appreciate it if you would give us some information which of the recent top 15 requests are on the roadmap for the next 12 month: JRA-3821 Priorities per Project and Resolutions per Issue Type JRA-4446 Sub-issues should be able to contain their own sub-issues JRA-1549 Ability to rename a user JRA-846 Support for subcomponents JRA-3156 Required: Project Group Administrator JRA-5783 Make field required only for one state transition JRA-5225 ( JRA-18505 ) Sub-tasks should inherit selectable fields from the parent task JRA-1391 Renaming groups after creation. JRA-5493 ( JRA-18505 ) Ability to add watchers during issue creation JRA-7266 Create a web-based email template editor - rather than having to edit Velocity templates JRA-3501 Allow Versions of components JRA-1991 Custom fields for Projects JRA-2698 Create versions on multiple projects JRA-7659 Limit user picker to members of certain groups / roles JRA-2703 Not possible to change a project's key Regards Thomas
          Hide
          Brett Ryan added a comment -

          Atlassian is quite unique in that we allow all end users to create bugs / feature requests directly, without having to go through a support system.

          Why do we bother raising requests when they're always closed? It would be great if we could see what's on the horizon and why some of these vital features keep getting a "Won't Fix" status.

          Every time I see one of these notices (and I've seen many) it makes me feel like you guys really couldn't give a rats for the user-community of the software.

          Show
          Brett Ryan added a comment - Atlassian is quite unique in that we allow all end users to create bugs / feature requests directly, without having to go through a support system. Why do we bother raising requests when they're always closed? It would be great if we could see what's on the horizon and why some of these vital features keep getting a "Won't Fix" status. Every time I see one of these notices (and I've seen many) it makes me feel like you guys really couldn't give a rats for the user-community of the software.
          Hide
          Barett Milligan added a comment -

          I don't understand how this has not been a higher priority on the JIRA roadmap. This has been a feature request from the user community since 2008.

          Show
          Barett Milligan added a comment - I don't understand how this has not been a higher priority on the JIRA roadmap. This has been a feature request from the user community since 2008.
          Hide
          Andy Brook (Javahollic Software) added a comment -

          @barett. It's not fixed because its not trivial, its quite complex. Also, it has a restricted audience, admins, therefore the same drivers do not apply as for a user-facing editor. Administrators who want to customize need to get to grips with the technologies involved.

          Complexities also come from having different layouts, loop semantics etc. Implementing a nice wysiwyg interface just introduces another layer of meta-layout and round-tripping problems. Velocity is a templating language, its being used for exactly that.

          I wonder, would having the ability to preview the result of edit be a halfway house? This would be somewhat like the wiki markup edit/preview of old.

          Just to bring up my JEMH feature set up to date, currently the integrated IssueListener now has a JIRA listener as well. This means that you could disconnect JIRA projects from their notification scheme and use JEMH, with its customizable TemplateSets, but without a preview mode, yet.

          Show
          Andy Brook (Javahollic Software) added a comment - @barett. It's not fixed because its not trivial, its quite complex. Also, it has a restricted audience, admins, therefore the same drivers do not apply as for a user-facing editor. Administrators who want to customize need to get to grips with the technologies involved. Complexities also come from having different layouts, loop semantics etc. Implementing a nice wysiwyg interface just introduces another layer of meta-layout and round-tripping problems. Velocity is a templating language, its being used for exactly that. I wonder, would having the ability to preview the result of edit be a halfway house? This would be somewhat like the wiki markup edit/preview of old. Just to bring up my JEMH feature set up to date, currently the integrated IssueListener now has a JIRA listener as well. This means that you could disconnect JIRA projects from their notification scheme and use JEMH, with its customizable TemplateSets, but without a preview mode, yet.
          Hide
          L. Fobel added a comment -

          I agree that the implementation is not trivial, but I completely disagree that the implementation would only benefit admins. My users don't like the canned look of the e-mail they receive from JIRA. The really don't like the canned look of the MS Word View.

          What I care about is an application that requires very little customization since every time there is a JIRA update, all of my customizations don't work and I have to wade through JIRA forums to find out how I need to redo my customizations.

          Why so much time and effort was put into developing the graphical interface for the workflows vs. addressing the issue is beyond me. Configuring the workflows was easy to do BEFORE the graphical interface, but customizing e-mail or printable views is still beyond difficult.

          Show
          L. Fobel added a comment - I agree that the implementation is not trivial, but I completely disagree that the implementation would only benefit admins. My users don't like the canned look of the e-mail they receive from JIRA. The really don't like the canned look of the MS Word View. What I care about is an application that requires very little customization since every time there is a JIRA update, all of my customizations don't work and I have to wade through JIRA forums to find out how I need to redo my customizations. Why so much time and effort was put into developing the graphical interface for the workflows vs. addressing the issue is beyond me. Configuring the workflows was easy to do BEFORE the graphical interface, but customizing e-mail or printable views is still beyond difficult.
          Hide
          Andy Brook (Javahollic Software) added a comment -

          I didn't say benefit, I said audience, meaning actual interacting users with the 'editor'. If they don't like the look and feel, you can customize, its up to you. I'm not clear how MS Word View relates to this issue?

          Customization management is a cost, you do it eyes open understanding the associated costs of maintaining them, or don't do them.

          The workflow editor was written by a 3rd party, Atlassian bought it (I think).

          Given text and html outputs are still required, Velocity is still appropriate and viable (even if it gives you some pain customizing). Yes there is complication with macros, interdependent velocity pages (some might call this a modular approach), comes with the territory, I honestly don't see this changing soon.

          Future discussion might be better hosted on https://answers.atlassian.com/questions/ ?

          Show
          Andy Brook (Javahollic Software) added a comment - I didn't say benefit, I said audience, meaning actual interacting users with the 'editor'. If they don't like the look and feel, you can customize, its up to you. I'm not clear how MS Word View relates to this issue? Customization management is a cost, you do it eyes open understanding the associated costs of maintaining them, or don't do them. The workflow editor was written by a 3rd party, Atlassian bought it (I think). Given text and html outputs are still required, Velocity is still appropriate and viable (even if it gives you some pain customizing). Yes there is complication with macros, interdependent velocity pages (some might call this a modular approach), comes with the territory, I honestly don't see this changing soon. Future discussion might be better hosted on https://answers.atlassian.com/questions/ ?
          Hide
          Andy Brook (Javahollic Software) added a comment -

          Bryan? The JEMH IssueListener supports the association of Project to Notification Scheme, so JEMH supports Internal and External users with potentially different templates for each. Could you please update the description?

          Show
          Andy Brook (Javahollic Software) added a comment - Bryan? The JEMH IssueListener supports the association of Project to Notification Scheme, so JEMH supports Internal and External users with potentially different templates for each. Could you please update the description?
          Hide
          Bryan Rollins [Atlassian] added a comment -

          Done. Thanks for the catch and correction, Andy!

          Show
          Bryan Rollins [Atlassian] added a comment - Done. Thanks for the catch and correction, Andy!
          Hide
          Toomas Romer added a comment -

          Maybe start off small and have ways to change those very same velocity templates instead of a full blown wysiwyg editor and stuff?

          Show
          Toomas Romer added a comment - Maybe start off small and have ways to change those very same velocity templates instead of a full blown wysiwyg editor and stuff?
          Hide
          Neeme Praks added a comment -

          Editing Velocity templates would be a good start! Also on Atlassian On-Demand.

          Show
          Neeme Praks added a comment - Editing Velocity templates would be a good start! Also on Atlassian On-Demand.
          Hide
          Alexander J. Drueppel added a comment -

          @Andy Brook:

          We need to customize a text block in subscription e-mails (different e-mail text per subscription!!!)

          Does JIRA Enterprise Mail Handler (JEMH) bring a solution for:

          Custom text on subscription e-mails configured through Admin GUI
          https://jira.atlassian.com/browse/JRA-23000

          or is there any other solution to customize text blocks per subscription?

          Show
          Alexander J. Drueppel added a comment - @Andy Brook: We need to customize a text block in subscription e-mails ( different e-mail text per subscription!!! ) Does JIRA Enterprise Mail Handler (JEMH) bring a solution for: Custom text on subscription e-mails configured through Admin GUI https://jira.atlassian.com/browse/JRA-23000 or is there any other solution to customize text blocks per subscription?
          Hide
          Andy Brook [The Plugin People] added a comment -

          Hi Alex, filter subscriptions are dealt with by JIRA internally, as yet, not something JEMH has done. Gives some ideas though.

          Show
          Andy Brook [The Plugin People] added a comment - Hi Alex, filter subscriptions are dealt with by JIRA internally, as yet, not something JEMH has done. Gives some ideas though.
          Hide
          Alexander J. Drueppel added a comment -

          @all: Is there any other solution to customize text blocks per subscription?

          Show
          Alexander J. Drueppel added a comment - @all: Is there any other solution to customize text blocks per subscription?
          Hide
          Tibor Hegyi added a comment -

          Hi Alex, have you tried to customize the JIRA subscription template itself? The file is called filtersubscription.vm and is located in WEB-INF/classes/templates/emaI/html or /text.
          You have access to the subscription object itself and to a bunch of JIRA components that may help you implement the customization.

          I know you were looking for a web based editor but there isn't any available yet.
          If you need help to customize the templates, feel free to contact me.

          Tibor

          Show
          Tibor Hegyi added a comment - Hi Alex, have you tried to customize the JIRA subscription template itself? The file is called filtersubscription.vm and is located in WEB-INF/classes/templates/emaI/html or /text. You have access to the subscription object itself and to a bunch of JIRA components that may help you implement the customization. I know you were looking for a web based editor but there isn't any available yet. If you need help to customize the templates, feel free to contact me. Tibor
          Hide
          Renjith [Atlassian] added a comment -

          A basic web based velocity template editor has been released (JIRA 6.x) under labs:

          https://marketplace.atlassian.com/plugins/com.atlassian.labs.jira.emaileditor.emaileditor-jira-plugin

          Show
          Renjith [Atlassian] added a comment - A basic web based velocity template editor has been released (JIRA 6.x) under labs: https://marketplace.atlassian.com/plugins/com.atlassian.labs.jira.emaileditor.emaileditor-jira-plugin
          Hide
          Patrik Dibdiak added a comment -

          When will you make the JIRA Outgoing Email Template Editor available for OnDemand?

          Show
          Patrik Dibdiak added a comment - When will you make the JIRA Outgoing Email Template Editor available for OnDemand?
          Hide
          Christoph Diefenthal added a comment -

          how can you change the subject of a mail? the templates do only manage the content, right?

          Show
          Christoph Diefenthal added a comment - how can you change the subject of a mail? the templates do only manage the content, right?
          Hide
          Christoph Diefenthal added a comment -

          you mean to change the subject? which issue is this? is there a solution available?

          Show
          Christoph Diefenthal added a comment - you mean to change the subject? which issue is this? is there a solution available?
          Hide
          Sorin Sbarnea (CITRIX) added a comment -

          Sometimes a different approach can fix the same problem: many people are asking about customizing the Jira templates because:

          • they are not accesible - the important information is not at the begining of the message
          • the HTML variant was not designed properly. Being able to use markup does not mean you have to make the email unreadable on small screen devices (and not only!). Always respect the screen real-estate and put the important information to the top of the message.
          • URLs are too long, find a way to shorthen them

          Now, I am sure that a smart redesign (as opposed to cheap paint-job...) would make most people not looking for customizing them anymore.

          Regarding customization take a look at how others are implementing templates and allow admins to customize the templates without loosing the changes on upgrades. This is not hard to implement but you need someone that has experience with these in order to design it correctly (easy to use and easy to implement).

          Show
          Sorin Sbarnea (CITRIX) added a comment - Sometimes a different approach can fix the same problem: many people are asking about customizing the Jira templates because: they are not accesible - the important information is not at the begining of the message the HTML variant was not designed properly. Being able to use markup does not mean you have to make the email unreadable on small screen devices (and not only!). Always respect the screen real-estate and put the important information to the top of the message. URLs are too long, find a way to shorthen them Now, I am sure that a smart redesign (as opposed to cheap paint-job...) would make most people not looking for customizing them anymore. Regarding customization take a look at how others are implementing templates and allow admins to customize the templates without loosing the changes on upgrades. This is not hard to implement but you need someone that has experience with these in order to design it correctly (easy to use and easy to implement).
          Hide
          Marian Ares added a comment -

          Is available yet the Outgoing Email Template Editor for OnDemand version? Thanks

          Show
          Marian Ares added a comment - Is available yet the Outgoing Email Template Editor for OnDemand version? Thanks
          Hide
          Alex added a comment -

          We need this too

          Show
          Alex added a comment - We need this too

            People

            • Assignee:
              Unassigned
              Reporter:
              Benjamin Naftzger [Atlassian]
            • Votes:
              537 Vote for this issue
              Watchers:
              269 Start watching this issue

              Dates

              • Created:
                Updated: