Created 08/Jul/2005 Coming up 20 year anniversary soon!
Such a simple, VERY USEFUL feature, but I guess it does not add revenue, so Atlassian don't have any interest.

Any new progress?

dmeyer You forgot to close this ticket.

I won't believe this basic function is still not implemented...

Any progress here?

Up!!

As apps were asked for, and this issue is a closed/wontfix:  We are the vendor of the Enterprise Mail Handler for Jira (cloud version available) JEMHC that supports email template customisation, its still velocity because, well, templates, you can use images and custom css if you like.  You can read about how values are extracted from webhooks for injection into templates here. 

We use https://marketplace.atlassian.com/apps/4977/email-this-issue?hosting=cloud&tab=overview

It uses a separate mailbox (so you cannot use the build in mailbox) but it gives you a lot more options to configure templates/triggers.

I would gladly do it, can you or anyone point me to one? I haven't found an alternative. Thanks

@Vincent Peres, purchasing an addon that can do it...

Hi, we are now forced by JIRA to move to the Cloud and we need something similar to editing email templates on the server. What are your suggestions?

Roman, too late your "+1"

Issue "resolved" 2 years ago - "Won't Fix" 

+1 for this

+1 for this. I want to be able to customize the contents of the notification mails that are sent to my agents

we do not have any plans to introduce support for custom email templates in JIRA Core or JIRA Software.

Well, on JRASERVER-7266 it was just announced that:

We plan to implement this feature in Jira Software and Core in the near future

Also, there is a suggestion on that same issue:

For Jira Cloud, please comment on the issue at JRACLOUD-7266

Time to reopen this issue?

Thanks Andy, I'll check it out. Seems like such a basic option...

Paul, it is possible with JEMHC which provides an editor and the means to inject fields. Atlassian have closed this as wont fix, its isn't going to be in the platform anytime soon.

Our Engineering team would like to always have the Status in issue notifications, however this isn't possible in Cloud. Please fix.

+1 for reopening this issue.

Custom events creation is available to the cloud instance, but it cannot relay on customized email template. In my usage both cannot be separated, we want to send a customized message to people when a specific event raises.

Thanks 

The sad part is that your tech support is still referencing this ticket and strongly encouraging us to visit and vote to have this made as a feature in JIRA CLOUD.

For those wanting customization, we implemented notification template customization support as part of Enterprise Mail Handler for Jira Cloud (JEMHC) and Server (JEMH).  Both versions still velocity, because its a good templating language.  Writing a funky editor is for us also, in the too hard basket at this time.  Both Cloud and Server versions allow edit time preview of templates in the context of an issue, so you're not flying blind.

 Cloud apps run as a service, as such, volume has to be capped (don't expect unlimited load/volume for 5$). JEMHC allocates capacity plans based on users so if you're a high volume / low user customer, then it will end up costing more as you'll burn through the allocation (you know who you are ).  If you want unlimited volume, pony up for the Server version of JIRA where you foot the infrastructure bill.

Agree with all the above - please re-open

I'm surprised you closed this issue - Issue tracking is all about communication and was the key feature in Serena's product at my last company that helped me sell it to various teams and executives across the company where we could send customized emails based on transition triggers back to our clients and teams so the emails were clear and we could subscribe to the various triggers so we don't get inundated with unnecessary emails we don't want or need. Esp with execs, we had it so they only saw on subject "Approval Request" then in the body, what they are approving - not all fields. Currently seeing all fields and trying to figure out what was updated is frustrating. I really hope you consider reopening this ticket and moving forward. I'm on the cloud version of course.

Please resurrect this issue.  The current format for the e-mail issued is of no use to users currently.  They need to be able to see a meaning full subject line - the issue number is not relevant, when you have over 5,000 tickets in the system.

Is this completely off the roadmap with a blocker being JRACLOUD-1369? I lack the understanding of why that would be a blocker for this specific ticket to continue.

The priority decision to focus on tuning the process of sending nearly useless emails over improving the email content is a bad decision. Modern mail programs have lots of features for managing the email volume, so while some might be annoyed by the volume, it's not urgent that you fine tune the sending. Furthermore, email rules only work if the content can be aligned with the mail rules. You've created a problem because we can't use mail rules effectively with the current default messages, but instead fixing the messages you are trying to add more features to control the sending. Having control over the email content solves BOTH problems. That is, it makes the email usable and it allows users to manage the messages better using the mail system they already have in place. Please revisit this poor decision.

We are swamped with emails on tickets.

Having the ticket status on the subject line could save us the need to enter the mail, click the link to go to the actual ticket and than see the status of the ticket.

Is there an easier approach to just edit the subject line? That's all I really need. The existing subect lines that come with the software are crap.

Dave Meyer wrote "We are committed to improving the notifications experience in JIRA Cloud over time."   

With respect Dave Meyer, it has been 12 years, 1419 votes, 601 watchers and 142 comments.   Meanwhile we still have automated communications going out from JIRA Service desk cloud that make our company look bad and us look stupid for using your product.

Dave Meyer wrote "Our priority is to focus first on sending the right amount of notifications at the right time (JRACLOUD-1369) and then we can consider adding additional customization options in the future."

JRACLOUD-1369 originated in 2003 and you are referencing that as your priority, while holding out a potential for customizations in the "future"?   Sorry, 2017 expects a more Agile response than this.  This response is not just disappointing, it is scary.

We currently struggle with the inability to include key pieces of information obtained in our Service Desk portal in our internal email notifications that help us more easily route and triage support cases that come in. For example, configuring a new ticket notification to include the organization or request type helps us decide and route the ticket to the appropriate group more easily. Likewise, we get LITTERED with support customers ignoring or thinking the new service desk account activation emails (portal only users) are spam or phishing attempts. Extend what you have allowed for configuration of EXTERNAL emails to the internal emails and allow configuration of the new customer account activation emails. DONE. Please reconsider!

I expect atlassian can do something which Jira Cloud Customers is actually get benefits of, i was in impression that being such a great company you 'd have introduced this features, Sadly this creates huge disappointments for JIRA Cloud customers.

Not bad, it was #3 issue by number of votes.

Really? After 12 years if waiting? I think someone just decided to close all old unresolved tickets without looking at customer needs!!

Wow. That was..... unexpected. Given that you CAN provide the template editor, since you provide it in Service Desk, it seems like a small step to offer this feature as an add-on, for a price of course. I have the feeling that a significant number of the 1419 voters and 608 watchers would be willing to pay for the ability to manage their email templates.

Atlassian, please reconsider your position on this request and ensure that you do not lose the good will of your users.

Thanks!

Hi everyone,

In the spirit of transparency, we are going to close this feature request for JIRA Cloud. It's been 18 months since we last provided an update and we do not have any plans to introduce support for custom email templates in JIRA Core or JIRA Software. (This is how we've been interpreting this feature request, as editing velocity templates has never been possible for JIRA Cloud). If you are a JIRA Server customer, please continue watching JRASERVER-7266 for updates.

JIRA Service Desk supports customizable email notifications for requests with HTML, CSS, and plaintext templates and custom variables. You can learn more about configuring custom notifications in the JIRA Service Desk in the JIRA Service Desk Cloud documentation.

For some cases where you want special email notifications for certain events (like the one mentioned in the comment immediate before this one), the most straightforward workaround may be to use a service like Zapier or IFTTT to receive webhooks from JIRA Cloud and send an email customized to your needs.

We are committed to improving the notifications experience in JIRA Cloud over time. Our priority is to focus first on sending the right amount of notifications at the right time (JRACLOUD-1369) and then we can consider adding additional customization options in the future.

Regards,
Dave Meyer
JIRA Product Management

Bump! Executives in my company are asking me to make this a reality so that the "APPROVAL" emails don't have the same plain header as the other notifications. Please Address!

Hi All, I am not so interested in custom email templates, I would just like to have comments added during a transition guaranteed to be emailed from the post condition. Currently where a number of post conditions occur, only 1 email is received pertaining to actions against the ticket.

As I understand due to asynchronous nature of execution, order of execution is not guaranteed, or able to be prioritised. Perhaps some flag on the post condition saying 'this' post condition is the one that these are the post conditions I want to have an email for would be good.

Can we at least get custom template information moved to the Home directory instead of the application directory? That alone would vastly simplify upgrade processes.

We need the ability to have custom fields included in the email template

Is there anyway to get threading to work correctly with Outlook?  Our entire company is using outlook and conversation view doesn't work.  

Btw in the previous versions of JIRA the subjects were fine. I had a lot of filters which colored the emails in my Thunderbird, this way I saw the important (new and reopen), resolved and non-important (grey) tasks in the list and it saved ton of my time. Then Atlassian changed the subject to be always the same "because of better Google threading support". I hate these general subjects too and I can't change it because of no template editor is available in Cloud version. I am trying to think that this forced me to use boards more than emails, but for monitoring emails are better.

And I am not sure at all that Subject is that important for Google, because it should rely on the email headers instead, and the old style "various" subjects work perfectly too.

@neal: Thanks. Problem is, I want it for all other emails, but not on Jira. The problem is really that JIRA Cloud seems to have SUPER generic email subject lines. It's just the Ticket ID and # and summary, nothing else. So everything gets bundled together.

@evan: That is a Gmail problem, easily rectified in Gmail settings. Turn off conversation view. This is, apparently, a very polarizing issue. People either hate it or love it. I am in the "hate it" camp and cannot understand why anyone would like this.

This is super frustrating. Gmail is grouping all emails into threads, and this is causing my team to tune out important notifications when someone tags them. "Evan updated ENG-123" should show in a different thread than "Evan tagged you in a comment on ENG-123"

when to expect this feature, as a private company we don't follow themes and content provided by Atlassian. We have our theme. Please let know that is this feature is coming or not. that put impact on decision of purchase for this CMS

I just want to update the email content of the very first initial notification sent to a first time user to create a user account.

Users think this is spam, and don't action.  

I think Atlassian is waiting for votes to accumuate further so when someday this is implemented they can say at the summit that they have honoured some thousands of votes.

1300 votes !!!

I think they are waiting for 2017 votes at least 

How many votes is required to prioritize this issue ? This issue has been created in July 2005 and we're now in 2017 !!!

Bumped.  Important

Me too. We have a number of emails enabled, but there are a couple which are really important and I have no way to indicate these messages are any different than the others. I'm using JIRA Cloud so I don't even have a back end option to hack in a change. Prior to JIRA cloud, not having a UI was a pain, but with JIRA cloud not having a UI is a huge gaping hole.

I fully agree with Steve^^ on this one

This really is a shame.   This request is now 11 years old.  Flexible wording  and being able to brand every communication from a system is critical for any organization using a service desk.  If we were aware of this limitation when we made our choice, we would have chosen another product from another company.  There is a difference between being a satisfied customer, and being stuck.

Also the problem is, that it's still not possible to integrate custom field in mention e-mail emplate. That is **prerequisite for this suggestion.

So please vote for that guys: https://jira.atlassian.com/browse/JRA-63561

**thank you guys, Marc.