Why do Email Templates change how they look from 6.0 to 6.1,6.2

Owned by Andy Brook [Plugin People] (Unlicensed)
Feb 28, 2014
1 min read

This page describes the impact of this change and some workarounds for 5.0 and 6.0 users with customized templates.

Summary

JIRA Email Templates changed in JIRA 6.1, this restructured the entire template, and removed styling from the template.  Styling was auto injected later.  

Impact

If a JEMH TemplateSet has been created for any Issue Event, they will have 6.0 styling and markup that will not mesh with DEFAULT template notifications that are new in 6.1+

Noticeable Consequences

  • the template content is entirely different

  • the look and feel, JIRA 6.1+ templates look very different

  • images get inlined, meaning they show up when the email is opened without referring to an external site (JEMH implemented this for JIRA 6.0, so adopted its way for 6.1+)

Migrating Templates

JEMH cannot migrate templates.  The easiest way to migrate custom Template Sets is to create a new TemplateSet based on the new IssueEvent, and re-customize.  Templates don't change too often, fortunately.

My very customized HTML emails have styling, where did it come from?

The CSS Inliner above, injects CSS into HTML markup.  Users have found that if the HEAD section of the HTML email contains style blocks defining CSS, and those styles are referred in the HTML elements in the template, that the CSS Inliner does then not inject CSS, so custom styling is still possible.