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
          tfeeley 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
          tfeeley 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
          tfeeley 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
          tfeeley 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
          taoy 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
          taoy 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
          bkunkel 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
          bkunkel 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
          vthoule@pyxis-tech.com 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
          vthoule@pyxis-tech.com 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
          tmoore 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
          tmoore 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
          agilles 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
          agilles 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
          myrapandora Myra Chachkin 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
          myrapandora Myra Chachkin 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
          barryallard Barry Allard added a comment -

          This is very important to my clients.

          Show
          barryallard Barry Allard added a comment - This is very important to my clients.
          Hide
          circusdog 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
          circusdog 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
          dbates Daniel Bates added a comment -

          i would like to add a disclaimer to my email templates

          Show
          dbates Daniel Bates added a comment - i would like to add a disclaimer to my email templates
          Hide
          tom002 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
          tom002 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
          javahollic 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
          javahollic 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
          jmonroe 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
          jmonroe 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
          amacnamara 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
          amacnamara 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
          tef Fabrizio Galletti added a comment -

          If possible the personalization should be project related or associated

          Show
          tef Fabrizio Galletti added a comment - If possible the personalization should be project related or associated
          Show
          rwinacott@vixs.com 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
          cxj 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
          cxj 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
          lchandler 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
          lchandler 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
          mdoar 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
          mdoar 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
          lchandler 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
          lchandler 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
          javahollic 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
          javahollic 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
          tom002 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
          tom002 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 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 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
          barettm 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
          barettm 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
          javahollic 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
          javahollic 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
          lfobel 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
          lfobel 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
          javahollic 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
          javahollic 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
          javahollic 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
          javahollic 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
          brollins Bryan Rollins [Atlassian] added a comment -

          Done. Thanks for the catch and correction, Andy!

          Show
          brollins Bryan Rollins [Atlassian] added a comment - Done. Thanks for the catch and correction, Andy!
          Hide
          toomas 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 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 Neeme Praks added a comment -

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

          Show
          neeme.praks Neeme Praks added a comment - Editing Velocity templates would be a good start! Also on Atlassian On-Demand.
          Hide
          alexander.drueppel 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.drueppel 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
          javahollic@gmail.com 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
          javahollic@gmail.com 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.drueppel Alexander J. Drueppel added a comment -

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

          Show
          alexander.drueppel Alexander J. Drueppel added a comment - @all: Is there any other solution to customize text blocks per subscription?
          Hide
          tibor 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 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
          rpillai 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
          rpillai 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@hanzoarchives.com Patrik Dibdiak added a comment -

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

          Show
          patrik.dibdiak@hanzoarchives.com Patrik Dibdiak added a comment - When will you make the JIRA Outgoing Email Template Editor available for OnDemand?
          Hide
          christoph.diefenthal 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 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 Christoph Diefenthal added a comment -

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

          Show
          christoph.diefenthal Christoph Diefenthal added a comment - you mean to change the subject? which issue is this? is there a solution available?
          Hide
          intersol Sorin Sbarnea 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
          intersol Sorin Sbarnea 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 Marian Ares added a comment -

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

          Show
          marian.ares Marian Ares added a comment - Is available yet the Outgoing Email Template Editor for OnDemand version? Thanks
          Hide
          alexandre.nshimiyimana@msp.gouv.qc.ca Alex added a comment -

          We need this too

          Show
          alexandre.nshimiyimana@msp.gouv.qc.ca Alex added a comment - We need this too
          Hide
          fklomp Frank Klomp added a comment -

          Why is this not a standard feature of JIRA onDemand? Sounds like a standard requirement I'd say.

          Show
          fklomp Frank Klomp added a comment - Why is this not a standard feature of JIRA onDemand? Sounds like a standard requirement I'd say.
          Hide
          helen1 Cleveron OÜ added a comment -

          My company needs this feature too, so please make it possible for ondemand.

          Show
          helen1 Cleveron OÜ added a comment - My company needs this feature too, so please make it possible for ondemand.
          Hide
          atlassian521 Sebastian Mendel added a comment -

          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.

          Would be nice if https://marketplace.atlassian.com/plugins/com.atlassian.labs.jira.emaileditor.emaileditor-jira-plugin can be upgraded for Jira 6.2

          Show
          atlassian521 Sebastian Mendel added a comment - 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. Would be nice if https://marketplace.atlassian.com/plugins/com.atlassian.labs.jira.emaileditor.emaileditor-jira-plugin can be upgraded for Jira 6.2
          Show
          vankudinov Vladimir Ankudinov added a comment - + 1 Would be nice if https://marketplace.atlassian.com/plugins/com.atlassian.labs.jira.emaileditor.emaileditor-jira-plugin can be upgraded for Jira 6.2
          Hide
          matt.doar Matt Doar [ServiceRocket] added a comment -

          My review on that add-on is:

          "No documentation! Hint: Admin, System, Mail. Good enough start but you still have to edit dozens of files to make a single change for all events and the real blocker is: "You need to restart JIRA for the changes to come to effect ". Without that I may as well edit the templates in my own favorite editor and use version control too."

          So I don't think it's a solution for this issue

          Show
          matt.doar Matt Doar [ServiceRocket] added a comment - My review on that add-on is: "No documentation! Hint: Admin, System, Mail. Good enough start but you still have to edit dozens of files to make a single change for all events and the real blocker is: "You need to restart JIRA for the changes to come to effect ". Without that I may as well edit the templates in my own favorite editor and use version control too." So I don't think it's a solution for this issue
          Hide
          fab242 Fabian Herz added a comment -

          Hello,

          I have a problem with this plugin. The templates are empty. Can someone help me?

          Show
          fab242 Fabian Herz added a comment - Hello, I have a problem with this plugin. The templates are empty. Can someone help me?
          Hide
          it301 OPSWAT IT Department added a comment -

          We are a customer that has just migrated from in-house JIRA (where we had personally customized our e-mail subject-line templates to read "Created" on any newly-created ticket) to JIRA OnDemand. Lack of e-mail subject-line customization templates in Jira OnDemand makes it impossible for my support team to determine which tickets to escalate (all newly created tickets) as is necessary for timely resolution of the tickets.
          Instead, the support team must now look at all tickets in order to determine which tickets are newly created (and therefore need immediate escalation) instead of being able to run a simple query which searches for all tickets containing the word "Created".
          I am hoping that with (currently) 600 votes, this ticket will soon become an action item for the Atlassian Development team.
          Thank you.

          Show
          it301 OPSWAT IT Department added a comment - We are a customer that has just migrated from in-house JIRA (where we had personally customized our e-mail subject-line templates to read "Created" on any newly-created ticket) to JIRA OnDemand. Lack of e-mail subject-line customization templates in Jira OnDemand makes it impossible for my support team to determine which tickets to escalate (all newly created tickets) as is necessary for timely resolution of the tickets. Instead, the support team must now look at all tickets in order to determine which tickets are newly created (and therefore need immediate escalation) instead of being able to run a simple query which searches for all tickets containing the word "Created". I am hoping that with (currently) 600 votes, this ticket will soon become an action item for the Atlassian Development team. Thank you.
          Hide
          jjimenezbhp Jose Jimenez added a comment -

          +1

          Show
          jjimenezbhp Jose Jimenez added a comment - +1
          Hide
          andy11 Andy Brook added a comment - - edited

          OPSWAT, just noticed your ref to JIRA Cloud. JEMHC (the cloud flavour of JEMH) is now available for JIRA Cloud. It has fully customizable templates and subjects, I think, the only addon to offer this right now.

          Show
          andy11 Andy Brook added a comment - - edited OPSWAT, just noticed your ref to JIRA Cloud. JEMHC (the cloud flavour of JEMH) is now available for JIRA Cloud. It has fully customizable templates and subjects, I think, the only addon to offer this right now.
          Hide
          cmauro Cristian Mauro added a comment -

          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. -> Outgoing Email Template Editor for JIRA
          by Atlassian Labs for JIRA Server 6.0 - 6.0.8

          Show
          cmauro Cristian Mauro added a comment - 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. -> Outgoing Email Template Editor for JIRA by Atlassian Labs for JIRA Server 6.0 - 6.0.8
          Hide
          nada.oneal Nada O'Neal added a comment -

          The problem with the Atlassian Labs plugin is that no one is running 6.0-6.0.8 in production at this point.

          Show
          nada.oneal Nada O'Neal added a comment - The problem with the Atlassian Labs plugin is that no one is running 6.0-6.0.8 in production at this point.
          Hide
          v_thoule Vincent Thoulé added a comment -

          Have a look on "Email This Issue" (https://marketplace.atlassian.com/plugins/com.metainf.jira.plugin.emailissue).
          I used it for a couple of client and it does the job for the Mail Templates.

          Related the Mail Handler feature, I do not have experience.

          Vincent

          Show
          v_thoule Vincent Thoulé added a comment - Have a look on "Email This Issue" ( https://marketplace.atlassian.com/plugins/com.metainf.jira.plugin.emailissue ). I used it for a couple of client and it does the job for the Mail Templates. Related the Mail Handler feature, I do not have experience. Vincent
          Hide
          rob.kearey Rob Kearey added a comment -

          Wit all respect to the various plugin makers, this should be a core feature of the basic product. It's been a decade now.

          Show
          rob.kearey Rob Kearey added a comment - Wit all respect to the various plugin makers, this should be a core feature of the basic product. It's been a decade now.
          Hide
          rudey.yao Rudey Yao [GLiNTECH] added a comment -

          Life for JIRA Admin would be easier if email templating can be done within the UI rather than in file system.

          Show
          rudey.yao Rudey Yao [GLiNTECH] added a comment - Life for JIRA Admin would be easier if email templating can be done within the UI rather than in file system.
          Hide
          usamais U I added a comment -

          JIRA emails are a basis of many other systems in our company and it would br great to easily/safely edit the Velocity templates

          Show
          usamais U I added a comment - JIRA emails are a basis of many other systems in our company and it would br great to easily/safely edit the Velocity templates
          Hide
          frederick.coutret Frédérick Coutret added a comment -

          We are a JIRA Cloud customer. I understand we should have a look at Atlasssian Connect but an easy and quick workaround would be to provide a few more email templates that we can assign to events. We want to replace the JIRA prefix in every email topic, this doesn't bring any value, and replace it by the system title name. If not possible can we just have a email template without the JIRA prefix ?

          By the way I can't find a description of all the email template that are provided in JIRA Cloud, have to test them one by one. Is there something documented ?

          Thank you

          Show
          frederick.coutret Frédérick Coutret added a comment - We are a JIRA Cloud customer. I understand we should have a look at Atlasssian Connect but an easy and quick workaround would be to provide a few more email templates that we can assign to events. We want to replace the JIRA prefix in every email topic, this doesn't bring any value, and replace it by the system title name. If not possible can we just have a email template without the JIRA prefix ? By the way I can't find a description of all the email template that are provided in JIRA Cloud, have to test them one by one. Is there something documented ? Thank you
          Hide
          javahollic@gmail.com Andy Brook [The Plugin People] added a comment -

          Hi Frédérick,
          1) You cant modify JIRACloud email templates within JIRA
          2) Remoting notifications (enabling content and subject changes) in JIRACloud is what JEMHC does (as well as inbound mail processing), it gives full control over Customizing Email Content, Manipulating Webhook data as well as Localisation and Themeing (css)

          Show
          javahollic@gmail.com Andy Brook [The Plugin People] added a comment - Hi Frédérick, 1) You cant modify JIRACloud email templates within JIRA 2) Remoting notifications (enabling content and subject changes) in JIRACloud is what JEMHC does (as well as inbound mail processing), it gives full control over Customizing Email Content , Manipulating Webhook data as well as Localisation and Themeing (css)
          Hide
          ognatkevych Oleksii Gnatkevych added a comment -

          I hope it will be implemented somewhere in JIRA 7.0, or 8.0, or 9.0, or 10.0, or 22.0.

          Show
          ognatkevych Oleksii Gnatkevych added a comment - I hope it will be implemented somewhere in JIRA 7.0, or 8.0, or 9.0, or 10.0, or 22.0.
          Hide
          lucille.green Lucille Green added a comment -

          Please could you reconsider this change?
          There is an issue with attachments and if we could place a footer that read something like: "To View any attachments please access the Customer Portal" which would go a long way in solving not only the attachments issues but a number of others.

          Show
          lucille.green Lucille Green added a comment - Please could you reconsider this change? There is an issue with attachments and if we could place a footer that read something like: "To View any attachments please access the Customer Portal" which would go a long way in solving not only the attachments issues but a number of others.
          Hide
          admin260 Morten Breiner added a comment -

          Hi,
          We are using JIRA Cloud for our support and it works very well. However, we have currently stopped expanding this further, due to the fact that we have now way of sending a meaning full email to clients, automatically created by a mail handler. We are currently considering how to progress from here.

          It would be really nice if the email template could be configurable and thereby allowing us to inform the new user, why he/she has received this email and how to progress from there. We need a working template functionality in JIRA Cloud urgently.

          Cheers
          -Morten

          Show
          admin260 Morten Breiner added a comment - Hi, We are using JIRA Cloud for our support and it works very well. However, we have currently stopped expanding this further, due to the fact that we have now way of sending a meaning full email to clients, automatically created by a mail handler. We are currently considering how to progress from here. It would be really nice if the email template could be configurable and thereby allowing us to inform the new user, why he/she has received this email and how to progress from there. We need a working template functionality in JIRA Cloud urgently. Cheers -Morten
          Hide
          andy11 Andy Brook added a comment -

          Lucille, JEMH does that as well as allowing attachments to be included on outbound mail if you wanted.
          Morten, that's the feature set JEMHC is aimed at...

          Show
          andy11 Andy Brook added a comment - Lucille, JEMH does that as well as allowing attachments to be included on outbound mail if you wanted. Morten, that's the feature set JEMHC is aimed at...
          Hide
          info550 Brady Owens added a comment - - edited

          While I wholeheartedly respect the work that "The Plugin People" have done with JEMH and JEMHC this is a capability that SHOULD be in Jira - not a third party application. Atlassian is attempting to sell Jira as a help desk solution, as well as a development tool. In the development tool scope, I can see not offering the ability to edit email templates as it isn't that important. But when Atlassian decided to go after the support desk market, that changes things. Email template editing is BASIC functionality of ANY support desk service! Just happens to be the reason I am now paying Freshdesk for my support system rather than paying Atlassian because the functionality is far too limited to be an actual support desk service. I pay a little more for Freshdesk, but I get an enormous amount of capability that far exceeds Atlassian's offering in Jira Service Desk. Expressing my opinion and stating why Atlassian lost out on my additional monthly revenue. I love Jira for development, but it was not good enough to run my customer support.

          Show
          info550 Brady Owens added a comment - - edited While I wholeheartedly respect the work that "The Plugin People" have done with JEMH and JEMHC this is a capability that SHOULD be in Jira - not a third party application. Atlassian is attempting to sell Jira as a help desk solution, as well as a development tool. In the development tool scope, I can see not offering the ability to edit email templates as it isn't that important. But when Atlassian decided to go after the support desk market, that changes things. Email template editing is BASIC functionality of ANY support desk service! Just happens to be the reason I am now paying Freshdesk for my support system rather than paying Atlassian because the functionality is far too limited to be an actual support desk service. I pay a little more for Freshdesk, but I get an enormous amount of capability that far exceeds Atlassian's offering in Jira Service Desk. Expressing my opinion and stating why Atlassian lost out on my additional monthly revenue. I love Jira for development, but it was not good enough to run my customer support.
          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.
          Hide
          ronaldo.fabbi José Ronaldo Fabbi added a comment -

          Any plan to do something like that to Cloud (OnDemand) version of JIRA?

          Show
          ronaldo.fabbi José Ronaldo Fabbi added a comment - Any plan to do something like that to Cloud (OnDemand) version of JIRA?

            People

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

              Dates

              • Created:
                Updated: